← previous blocknext block →recent activity
Analyzing
Block #108,276,272
12 transactions · 12 stateful · 2026-09-26 20:37:18 UTC
Parallelism
83/100
Blocked
8%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,276,272 · 12 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
1w08w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc4f1f14…aa5f
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xbdd798e9…4b64
0x065c9d…c394
3 touches
1 conflict
0x0f9867f2…e315
0x065c9d…c394
2 touches
0 conflicts
0x45fd36aa…39c7
0x065c9d…c394
2 touches
0 conflicts
0x4ef6ba0f…5d78
0x065c9d…c394
2 touches
0 conflicts
0xa2972e0d…5b4d
0x065c9d…c394
2 touches
0 conflicts
0xdfa159d0…1576
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: Market-MON/USDC
1 conflict on slot 0xcc4f1f1446…7caa5f
Audit this contract →
← previous block·next block →recent activity