← previous blocknext block →recent activity
Analyzing
Block #108,655,319
20 transactions · 18 stateful · 2026-09-28 04:25:27 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,655,319 · 20 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
1w02w03w19w211w112w013w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33e9c0ba…08e6
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x71b64718…0ad1
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd8c20e6b…9a47
0x34b655…2a6f
4 touches
1 conflict
0x1f84ce8a…5acc
0x34b655…2a6f
4 touches
1 conflict
0x8cbe5084…d554
0xd32edf…ff58
3 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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: Perpl
1 conflict on slot 0x33e9c0ba3f…df08e6
Audit this contract →
← previous block·next block →recent activity