← previous blocknext block →recent activity
Analyzing
Block #108,516,476
21 transactions · 21 stateful · 2026-09-27 16:46:15 UTC
Parallelism
62/100
Blocked
67%
Avg conflicts / tx
1.57
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #108,516,476 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w08w19w210w311w412w513w414w515w616w717w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa03c2a35…52e6
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0x6aa624fd…a850
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 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 0xa03c2a355d…ca52e6
Audit this contract →
← previous block·next block →recent activity