← previous blocknext block →recent activity
Analyzing
Block #73,417,599
7 transactions · 6 stateful · 2026-05-09 08:03:07 UTC
Parallelism
57/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,417,599 · 7 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
1w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f483049…3cc7
0x34b655…2a6f
4 touches
1 conflict
0x77905798…fe3d
0x34b655…2a6f
4 touches
1 conflict
0x9ea57326…329f
0x34b655…2a6f
4 touches
1 conflict
0xd0a6cde5…29cc
0x34b655…2a6f
4 touches
1 conflict
0xd6aabe89…92f5
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfa2527aa…9dd5
0x34b655…2a6f
4 touches
1 conflict
0x1db301a1…dda1
0x34b655…2a6f
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: Perpl
1 conflict on slot 0x4f4830497d…d73cc7
Audit this contract →
← previous block·next block →recent activity