pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#73,970,776
← previous block
next block →
recent activity
Analyzing
Block #73,970,776
9 transactions · 8 stateful · 2026-05-11 21:40:46 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,970,776
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1ffa3c9b
· blocks 1
#2
execute
#4
forward
#5
closeTrade
#6
forward
#7
updateDataFeedsValuesPartial
#8
setData
#3
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51750603…1f93
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe355bf38…faf1
0x065c9d…c394
4 touches
1 conflict
0xc18afce7…5bdd
0x065c9d…c394
3 touches
1 conflict
0xcbc69bda…630b
0x065c9d…c394
3 touches
1 conflict
0xe362dee8…708f
0x065c9d…c394
3 touches
1 conflict
0xb23b5d23…2d2b
0x065c9d…c394
2 touches
0 conflicts
0xcea46e30…9563
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:
0x065c9d28…a9c394
1 conflict on slot
0x5175060313…a21f93
Audit this contract →
← previous block
·
next block →
recent activity