← previous blocknext block →recent activity
Analyzing
Block #108,509,580
11 transactions · 11 stateful · 2026-09-27 16:11:32 UTC
Parallelism
64/100
Blocked
45%
Avg conflicts / tx
0.82
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,509,580 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w17w18w29w310w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5dc501b…831c
0x34b655…2a6f
8 touches
6 conflicts
0x7bd229ad…63b2
0x34b655…2a6f
6 touches
3 conflicts
0xd739490d…821e
0x34b655…2a6f
6 touches
3 conflicts
0xcb45d9d6…cb85
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0xea7afae0…ef9c
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x152c6c76…d634
0xd32edf…ff58
5 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: Perpl
6 conflicts on slot 0xf5dc501bf7…74831c
Audit this contract →
← previous block·next block →recent activity