← previous blocknext block →recent activity
Analyzing
Block #108,787,523
24 transactions · 23 stateful · 2026-09-28 15:31:26 UTC
Parallelism
88/100
Blocked
30%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,787,523 · 24 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
2w03w04w15w06w17w015w116w017w018w119w221w022w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x0d54fa3e…3b3c
0x34b655…2a6f
4 touches
1 conflict
0x5acd9e7b…2eb2
0x34b655…2a6f
4 touches
1 conflict
0x6c09658a…d1d9
0x34b655…2a6f
4 touches
1 conflict
0x739123da…57f3
0x34b655…2a6f
4 touches
1 conflict
0x7bd229ad…63b2
0x34b655…2a6f
4 touches
1 conflict
0x88fc2a68…3918
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity