← previous blocknext block →recent activity
Analyzing
Block #108,610,183
12 transactions · 11 stateful · 2026-09-28 00:38:08 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,610,183 · 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
1w06w07w19w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf3d7a307…4d63
0x065c9d…c394
4 touches
1 conflict
0x3a663e9a…a9cb
0x508254…98bd
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x134411c7…4619
0x851145…3f07
4 touches
1 conflict
0x56c670b6…d526
0x851145…3f07
4 touches
1 conflict
0x8320df96…64c3
0x851145…3f07
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity