← previous blocknext block →recent activity
Analyzing
Block #81,876,276
20 transactions · 17 stateful · 2026-06-17 12:33:16 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #81,876,276 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w07w18w29w010w311w413w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x5581d709…ab77
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x112cf8ad…6e4f
0xa6afd3…d132
4 touches
1 conflict
0xfc578b53…9b1f
0xa6afd3…d132
4 touches
1 conflict
0x9966da31…0d0f
0x34b655…2a6f
2 touches
0 conflicts
0xa7a1d036…b8aa
0x34b655…2a6f
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
6 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity