← previous blocknext block →recent activity
Analyzing
Block #81,094,571
16 transactions · 13 stateful · 2026-06-13 21:46:42 UTC
Parallelism
88/100
Blocked
15%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #81,094,571 · 16 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
1w04w110w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x160f117d…8e90
0x065c9d…c394
4 touches
1 conflict
0xac8a5059…fd42
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x2a804d6b…1620
0x40c49f…2af0
2 touches
0 conflicts
0xaa2fefac…e4bd
0x40c49f…2af0
2 touches
0 conflicts
0xb11e9ce8…447d
0x40c49f…2af0
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 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity