← previous blocknext block →recent activity
Analyzing
Block #108,532,505
25 transactions · 24 stateful · 2026-09-27 18:06:55 UTC
Parallelism
72/100
Blocked
42%
Avg conflicts / tx
0.96
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,532,505 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w59w011w618w519w020w123w524w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5dc501b…831c
0x34b655…2a6f
12 touches
15 conflicts
0x7bd229ad…63b2
0x34b655…2a6f
10 touches
10 conflicts
0xcb45d9d6…cb85
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0002
0x125f12…a50b
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0x87b3c188…6ea2
0x34b655…2a6f
6 touches
3 conflicts
0xa69bb4e1…f2bb
0x34b655…2a6f
6 touches
3 conflicts
0x948577e7…0146
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
15 conflicts on slot 0xf5dc501bf7…74831c
Audit this contract →
← previous block·next block →recent activity