← previous blocknext block →recent activity
Analyzing
Block #106,533,056
19 transactions · 18 stateful · 2026-09-20 18:19:53 UTC
Parallelism
53/100
Blocked
61%
Avg conflicts / tx
2.16
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,533,056 · 19 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
1w02w13w24w15w37w210w311w412w513w614w715w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd41f5136…97c6
0x34b655…2a6f
16 touches
28 conflicts
0x2cd2af6f…b80f
0x34b655…2a6f
14 touches
21 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
0xd0ec60a1…d245
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
28 conflicts on slot 0xd41f513688…4197c6
Audit this contract →
← previous block·next block →recent activity