← previous blocknext block →recent activity
Analyzing
Block #81,004,053
13 transactions · 9 stateful · 2026-06-13 11:43:07 UTC
Parallelism
85/100
Blocked
11%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #81,004,053 · 13 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
1w02w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1d83e1f5…9d3e
0x065c9d…c394
2 touches
0 conflicts
0x3be89c0b…c354
0x065c9d…c394
2 touches
0 conflicts
0x8f83230a…1a0e
0x065c9d…c394
2 touches
0 conflicts
0xa2e19d83…4c94
0x065c9d…c394
2 touches
0 conflicts
0xc2042380…ebf8
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 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity