← previous blocknext block →recent activity
Analyzing
Block #108,309,810
20 transactions · 16 stateful · 2026-09-26 23:26:05 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,309,810 · 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
6w07w010w111w212w316w318w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa69bb4e1…f2bb
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x125f12…a50b
2 touches
0 conflicts
0x00000000…0009
0x125f12…a50b
2 touches
0 conflicts
0x00000000…0019
0x1b6862…e19c
2 touches
0 conflicts
0xcb45d9d6…cb81
0x1b6862…e19c
2 touches
0 conflicts
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity