← previous blocknext block →recent activity
Analyzing
Block #76,234,613
12 transactions · 8 stateful · 2026-05-22 09:33:06 UTC
Parallelism
83/100
Blocked
13%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,234,613 · 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0aa885fa…a3d1
0x2a68ba…90c5
4 touches
1 conflict
0xc0db09b2…81a0
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x2ddd4fb9…6778
0x065c9d…c394
2 touches
0 conflicts
0x2e4c8705…99d2
0x065c9d…c394
2 touches
0 conflicts
0xf3d7a307…4d63
0x065c9d…c394
2 touches
0 conflicts
0xfe2bac2b…2cec
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0000
0x139aab…382b
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 0x0aa885fa2f…33a3d1
Audit this contract →
← previous block·next block →recent activity