← previous blocknext block →recent activity
Analyzing
Block #106,534,292
20 transactions · 20 stateful · 2026-09-20 18:26:06 UTC
Parallelism
55/100
Blocked
55%
Avg conflicts / tx
1.6
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,534,292 · 20 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w07w08w010w111w112w213w314w415w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd41f5136…97c6
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x7a29f761…5f88
0x34b655…2a6f
10 touches
10 conflicts
0x86cea35b…bdff
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0x2b093939…9088
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
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
21 conflicts on slot 0xd41f513688…4197c6
Audit this contract →
← previous block·next block →recent activity