pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,210,913
24 transactions · 22 stateful · 2026-05-08 09:07:57 UTC
Parallelism
79/100
Blocked
41%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,210,913 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w06w07w18w010w011w112w213w114w218w119w222w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4730a2d…3538
0x34b655…2a6f
10 touches
10 conflicts
0x9553af3c…ecde
0x34b655…2a6f
8 touches
6 conflicts
0x387861df…0c8f
0xd32edf…ff58
5 touches
3 conflicts
0xa5fb9779…2384
0x34b655…2a6f
4 touches
1 conflict
0xac206e47…ef7d
0x34b655…2a6f
4 touches
1 conflict
0xad9f16b9…4f06
0x34b655…2a6f
4 touches
1 conflict
0x0335ae80…8414
0x8d66a4…3095
4 touches
1 conflict
0x143dba04…1b98
0x8d66a4…3095
4 touches
1 conflict
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: 0x34b6552d…112a6f
10 conflicts on slot 0xf4730a2de3…ef3538
Audit this contract →
← previous block·next block →recent activity