pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,500,071
12 transactions · 11 stateful · 2026-05-09 17:11:51 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,500,071 · 12 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
2w05w16w27w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90a13a85…8c93
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x3c02e4d1…494c
0x065c9d…c394
4 touches
1 conflict
0x1ef84ec0…7df0
0x065c9d…c394
4 touches
1 conflict
0x8c6960b5…31d5
0x065c9d…c394
4 touches
1 conflict
0x261567cc…5542
0x065c9d…c394
3 touches
1 conflict
0x9ed64890…96a0
0x065c9d…c394
3 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: 0x065c9d28…a9c394
1 conflict on slot 0x90a13a8531…df8c93
Audit this contract →
← previous block·next block →recent activity