← previous blocknext block →recent activity
Analyzing
Block #108,680,364
17 transactions · 16 stateful · 2026-09-28 06:31:35 UTC
Parallelism
59/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,680,364 · 17 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
1w02w13w24w38w39w410w512w615w116w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x732d4b2d…2590
0x34b655…2a6f
8 touches
6 conflicts
0x674b8cd1…ddf8
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0051
0x1b6862…e19c
6 touches
3 conflicts
0x5c421c70…c2eb
0x1b6862…e19c
6 touches
3 conflicts
0xba5743c7…21bf
0x1b6862…e19c
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: Perpl
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity