← previous blocknext block →recent activity
Analyzing
Block #101,068,117
16 transactions · 14 stateful · 2026-09-01 14:39:11 UTC
Parallelism
81/100
Blocked
36%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,068,117 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w110w013w214w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x1d9867ad…6d9a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x03515bce…2b96
0x065c9d…c394
3 touches
1 conflict
0x00000000…0036
0x35a73b…6042
2 touches
0 conflicts
0x408b5d36…096c
0x35a73b…6042
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
3 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity