← previous blocknext block →recent activity
Analyzing
Block #108,503,528
26 transactions · 20 stateful · 2026-09-27 15:41:04 UTC
Parallelism
77/100
Blocked
55%
Avg conflicts / tx
0.96
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,503,528 · 26 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w013w114w215w316w421w422w525w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc7b9eda…e616
0x34b655…2a6f
10 touches
10 conflicts
0x7b13dce8…b04d
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x368baece…4048
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x1f8a126c…9aa5
0x1b6862…e19c
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001c
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
10 conflicts on slot 0xdc7b9eda72…99e616
Audit this contract →
← previous block·next block →recent activity