← previous blocknext block →recent activity
Analyzing
Block #101,068,031
11 transactions · 9 stateful · 2026-09-01 14:38:45 UTC
Parallelism
82/100
Blocked
11%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,068,031 · 11 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
1w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07b86c51…cdae
0x2a68ba…90c5
4 touches
1 conflict
0x9e7e2c62…1637
0x851145…3f07
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x4213f1c0…219a
0x2a68ba…90c5
2 touches
0 conflicts
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0x80caf0f7…f2de
0x34ae4d…3fc5
2 touches
0 conflicts
0x085df2c1…305a
0x34b655…2a6f
2 touches
0 conflicts
0x0b7b942e…f3f4
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
1 conflict on slot 0x07b86c515d…73cdae
Audit this contract →
← previous block·next block →recent activity