← previous blocknext block →recent activity
Analyzing
Block #76,238,117
12 transactions · 9 stateful · 2026-05-22 09:56:26 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,238,117 · 12 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
1w02w13w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9bf064a6…4f04
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x0aa885fa…a3d1
0x2a68ba…90c5
4 touches
1 conflict
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0x0125d214…c84a
0xd32edf…ff58
3 touches
1 conflict
0xc67c3718…f30b
0x065c9d…c394
3 touches
1 conflict
0x54fc3b88…55de
0x065c9d…c394
3 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: Kuru Exchange: MarginAccount
1 conflict on slot 0x9bf064a6f8…394f04
Audit this contract →
← previous block·next block →recent activity