← previous blocknext block →recent activity
Analyzing
Block #73,038,610
18 transactions · 17 stateful · 2026-05-07 14:01:30 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,038,610 · 18 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
1w02w13w25w06w114w015w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf06c2cf5…61bd
0x34b655…2a6f
6 touches
3 conflicts
0x16fe810b…4402
0xd32edf…ff58
5 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x0f94ee4c…189e
0x1b6862…e19c
4 touches
1 conflict
0x388f889f…a655
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0335ae80…8414
0x8d66a4…3095
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 0xf06c2cf5e4…3161bd
Audit this contract →
← previous block·next block →recent activity