← previous blocknext block →recent activity
Analyzing
Block #106,386,127
23 transactions · 22 stateful · 2026-09-20 06:00:22 UTC
Parallelism
74/100
Blocked
64%
Avg conflicts / tx
1.61
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,386,127 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w17w28w29w310w420w421w522w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9e514894…86b0
0x34b655…2a6f
12 touches
15 conflicts
0x89eaf36a…4e48
0x34b655…2a6f
10 touches
10 conflicts
0x0ed7cc0b…ee52
0x34b655…2a6f
10 touches
10 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
10 touches
10 conflicts
0x70986451…c6bd
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xc78b8610…8ca1
0x34b655…2a6f
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 0x9e514894dc…1186b0
Audit this contract →
← previous block·next block →recent activity