← previous blocknext block →recent activity
Analyzing
Block #73,705,715
15 transactions · 11 stateful · 2026-05-10 16:07:02 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,705,715 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaa8a1c54…ead3
0x34b655…2a6f
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x8aa1941d…2988
0x34b655…2a6f
4 touches
1 conflict
0xa8bd52b5…862e
0x34b655…2a6f
4 touches
1 conflict
0xa92c8763…6d7f
0x34b655…2a6f
4 touches
1 conflict
0xabafe587…761b
0x34b655…2a6f
4 touches
1 conflict
0xbcb78361…78c7
0x34b655…2a6f
4 touches
1 conflict
0xd483830e…3e0c
0x34b655…2a6f
4 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: Perpl
3 conflicts on slot 0xaa8a1c5424…edead3
Audit this contract →
← previous block·next block →recent activity