← previous blocknext block →recent activity
Analyzing
Block #108,498,502
35 transactions · 31 stateful · 2026-09-27 15:15:45 UTC
Parallelism
71/100
Blocked
71%
Avg conflicts / tx
2.37
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #108,498,502 · 35 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w620w326w131w432w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
20 touches
45 conflicts
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0xde8b8098…3730
0xd32edf…ff58
13 touches
21 conflicts
0x2e84bea1…20bc
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x1f8a126c…9aa5
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…002c
0x1b6862…e19c
10 touches
10 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
45 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity