pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,372,692
9 transactions · 7 stateful · 2026-05-09 03:04:12 UTC
Parallelism
78/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,372,692 · 9 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f08361d…bda6
0x065c9d…c394
4 touches
1 conflict
0xf537eaa0…73c8
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x22e295f5…1bef
0x065c9d…c394
2 touches
0 conflicts
0x2bf43ce4…166c
0x065c9d…c394
2 touches
0 conflicts
0x51b9b594…4f66
0x065c9d…c394
2 touches
0 conflicts
0x6e6274e1…ae4d
0x065c9d…c394
2 touches
0 conflicts
0xa7fe0d97…ae1c
0x2a68ba…90c5
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 0x6f08361da9…89bda6
Audit this contract →
← previous block·next block →recent activity