pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,035,714
14 transactions · 10 stateful · 2026-05-07 13:42:13 UTC
Parallelism
79/100
Blocked
40%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,035,714 · 14 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
1w02w13w26w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xbd7e37a9…9eb5
0x065c9d…c394
6 touches
3 conflicts
0x1a4b4152…0a08
0x6ca43f…c331
6 touches
3 conflicts
0x3e4b8d9f…b8a7
0x6ca43f…c331
6 touches
3 conflicts
0x4e5ebbf7…ae70
0xc8689a…ee79
6 touches
3 conflicts
0x00000000…0002
0xd574ca…7ab1
6 touches
3 conflicts
0xc5564f8e…f4bf
0x6ca43f…c331
4 touches
2 conflicts
0xeb27550d…6028
0x6ca43f…c331
4 touches
2 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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity