← previous blocknext block →recent activity
Analyzing
Block #108,575,182
25 transactions · 20 stateful · 2026-09-27 21:41:56 UTC
Parallelism
80/100
Blocked
50%
Avg conflicts / tx
0.92
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,575,182 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w16w07w18w210w211w213w217w320w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x125f12…a50b
8 touches
6 conflicts
0xaeb22125…4a5f
0xd32edf…ff58
7 touches
6 conflicts
0xcca81b4b…ca75
0x065c9d…c394
7 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0xba38536d…2b7d
0x065c9d…c394
6 touches
3 conflicts
0xcb45d9d6…cb86
0x1b6862…e19c
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 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: 0x125f12a1…cda50b
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity