← previous blocknext block →recent activity
Analyzing
Block #73,463,458
11 transactions · 9 stateful · 2026-05-09 13:08:11 UTC
Parallelism
73/100
Blocked
44%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,463,458 · 11 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
1w04w16w17w29w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x88b4c5f8…3d7f
0x065c9d…c394
4 touches
1 conflict
0x3bf36078…cac6
0x065c9d…c394
4 touches
1 conflict
0x01337480…691e
0x065c9d…c394
3 touches
1 conflict
0xf14ad7d8…eae0
0x065c9d…c394
3 touches
1 conflict
0x97b8365d…8881
0x065c9d…c394
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity