← previous blocknext block →recent activity
Analyzing
Block #106,476,438
19 transactions · 19 stateful · 2026-09-20 13:34:55 UTC
Parallelism
58/100
Blocked
53%
Avg conflicts / tx
1.74
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,476,438 · 19 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
1w02w13w04w15w07w210w211w312w314w415w516w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xde00fca6…3969
0x34b655…2a6f
14 touches
21 conflicts
0x31d88d27…7617
0x34b655…2a6f
10 touches
10 conflicts
0x0262e1c6…52e1
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x8a02d049…f481
0x34b655…2a6f
6 touches
3 conflicts
0x5e3014f0…b4e1
0x34b655…2a6f
6 touches
3 conflicts
0x06a7c750…5d32
0x34b655…2a6f
4 touches
1 conflict
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 0xde00fca6f9…a23969
Audit this contract →
← previous block·next block →recent activity