← previous blocknext block →recent activity
Analyzing
Block #106,452,662
21 transactions · 20 stateful · 2026-09-20 11:35:16 UTC
Parallelism
62/100
Blocked
60%
Avg conflicts / tx
1.57
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,452,662 · 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
1w02w13w24w35w06w112w414w215w316w417w518w619w720w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x287ee53a…cb49
0x34b655…2a6f
12 touches
15 conflicts
0x0262e1c6…52e1
0x34b655…2a6f
10 touches
10 conflicts
0x06a7c750…5d32
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…001b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0xba5743c7…21c2
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
15 conflicts on slot 0x287ee53a56…39cb49
Audit this contract →
← previous block·next block →recent activity