← previous blocknext block →recent activity
Analyzing
Block #72,287,883
9 transactions · 7 stateful · 2026-05-04 02:39:50 UTC
Parallelism
78/100
Blocked
14%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,287,883 · 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
1w02w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3c8642a…7da5
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xfdd8e9b6…a97d
0x065c9d…c394
4 touches
1 conflict
0x5bd230c6…6274
0x065c9d…c394
3 touches
1 conflict
0xf14922de…2f4f
0x065c9d…c394
3 touches
1 conflict
0x8363ff8d…ee3b
0x065c9d…c394
3 touches
1 conflict
0x907a551c…508c
0x065c9d…c394
2 touches
0 conflicts
0xf25b5102…c100
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: Kuru Exchange: MarginAccount
1 conflict on slot 0xc3c8642ae9…317da5
Audit this contract →
← previous block·next block →recent activity