← previous blocknext block →recent activity
Analyzing
Block #108,548,964
11 transactions · 10 stateful · 2026-09-27 19:29:47 UTC
Parallelism
73/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,548,964 · 11 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
1w02w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x322bba8c…149e
0x065c9d…c394
4 touches
1 conflict
0x96102f0e…19f9
0xd32edf…ff58
3 touches
1 conflict
0xb282dc60…a182
0x065c9d…c394
3 touches
1 conflict
0xbbe479de…668f
0x065c9d…c394
3 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
2 touches
0 conflicts
0x39b7c3a7…0b72
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity