pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,336,067
← previous block
next block →
recent activity
Analyzing
Block #73,336,067
9 transactions · 9 stateful · 2026-05-08 23:00:33 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,336,067
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
updatePrices
#4
handleOps
#5
forward
#6
0x69fe6b88
#7
0xeffdedb0
#8
setData
#2
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a6cb118…4ca8
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x37179a7b…3f29
0xd32edf…ff58
3 touches
1 conflict
0x0452d0ff…758c
0x065c9d…c394
2 touches
0 conflicts
0x06d299ba…86ed
0x065c9d…c394
2 touches
0 conflicts
0x0c38465d…a3d8
0x065c9d…c394
2 touches
0 conflicts
0x2ec36e63…e389
0x065c9d…c394
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer:
ShMonad (shMON)
1 conflict on slot
0x0a6cb11882…264ca8
Audit this contract →
← previous block
·
next block →
recent activity