← previous blocknext block →recent activity
Analyzing
Block #72,311,258
9 transactions · 8 stateful · 2026-05-04 05:15:58 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,311,258 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xc146124f…400b
0x065c9d…c394
4 touches
1 conflict
0x0b6b8b2f…29e5
0x065c9d…c394
2 touches
0 conflicts
0x34c72c1c…401e
0x065c9d…c394
2 touches
0 conflicts
0xed560d92…3132
0x065c9d…c394
2 touches
0 conflicts
0xf3a64fde…2981
0x065c9d…c394
2 touches
0 conflicts
0x00000000…009a
0x16f70c…c3dd
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: Kuru Exchange: MarginAccount
1 conflict on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity