pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,501,306
13 transactions · 9 stateful · 2026-05-09 17:20:05 UTC
Parallelism
85/100
Blocked
22%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,501,306 · 13 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
1w05w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa8b7f0b7…d7ac
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x4d87512b…897c
0x065c9d…c394
4 touches
1 conflict
0x22e295f5…1bef
0x065c9d…c394
2 touches
0 conflicts
0x280e96ec…9825
0x065c9d…c394
2 touches
0 conflicts
0x45bf60e9…cb98
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
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 0xa8b7f0b7a0…edd7ac
Audit this contract →
← previous block·next block →recent activity