← previous blocknext block →recent activity
Analyzing
Block #106,452,913
21 transactions · 18 stateful · 2026-09-20 11:36:32 UTC
Parallelism
67/100
Blocked
61%
Avg conflicts / tx
1.14
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,452,913 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w15w29w310w011w312w413w514w515w617w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8874d9ad…4cf7
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xfdd131fa…dbdb
0x34b655…2a6f
6 touches
3 conflicts
0xec85b41e…7c93
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
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 0x8874d9adc7…5c4cf7
Audit this contract →
← previous block·next block →recent activity