← previous blocknext block →recent activity
Analyzing
Block #73,475,944
14 transactions · 11 stateful · 2026-05-09 14:31:17 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.29
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,475,944 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w17w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa91c899f…6ee3
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x3b53436c…2ec3
0x34b655…2a6f
4 touches
1 conflict
0x7f430e47…4cbd
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1a8
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1ac
0x8d66a4…3095
4 touches
1 conflict
0xe72962f6…e169
0x8d66a4…3095
4 touches
1 conflict
0x83cde744…b76b
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
1 conflict on slot 0xa91c899f02…fa6ee3
Audit this contract →
← previous block·next block →recent activity