pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,283,610
15 transactions · 13 stateful · 2026-05-04 02:11:04 UTC
Parallelism
80/100
Blocked
23%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,283,610 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w18w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6455d1f…1029
0x754704…b603
6 touches
3 conflicts
0x0d0b2509…074d
0x3bd359…433a
6 touches
3 conflicts
0xd77e90ec…8c04
0x3bd359…433a
4 touches
1 conflict
0x08943ea2…ed03
0x754704…b603
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
2 touches
0 conflicts
0x01e7b865…6e6e
0x188d58…ea8e
2 touches
0 conflicts
0x7c403af1…31b1
0x3bd359…433a
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: 0x754704bc…afb603
3 conflicts on slot 0xe6455d1fbe…eb1029
Audit this contract →
← previous block·next block →recent activity