← previous blocknext block →recent activity
Analyzing
Block #106,380,525
55 transactions · 50 stateful · 2026-09-20 05:32:10 UTC
Parallelism
64/100
Blocked
72%
Avg conflicts / tx
3.35
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #106,380,525 · 55 txs across 20 waves · depth 20
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w913w114w324w425w529w631w735w937w1140w1242w1544w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c10ef2f…8633
0x34b655…2a6f
22 touches
55 conflicts
0x00000000…0013
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…0015
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…001a
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…002a
0x1b6862…e19c
20 touches
45 conflicts
0x35801c67…bcc0
0x1b6862…e19c
20 touches
45 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…0012
0x1b6862…e19c
20 touches
45 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
55 conflicts on slot 0x4c10ef2f1b…798633
Audit this contract →
← previous block·next block →recent activity