pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,213,619
11 transactions · 9 stateful · 2026-05-03 18:20:45 UTC
Parallelism
82/100
Blocked
11%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,213,619 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x18bf2a65…005d
0x065c9d…c394
2 touches
0 conflicts
0x20404ffc…74ec
0x065c9d…c394
2 touches
0 conflicts
0x5db525e7…5bd6
0x065c9d…c394
2 touches
0 conflicts
0x77a88986…e5b8
0x065c9d…c394
2 touches
0 conflicts
0xb90c5fb2…f6e5
0x065c9d…c394
2 touches
0 conflicts
0xdb80d001…4874
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity