← previous blocknext block →recent activity
Analyzing
Block #106,272,539
27 transactions · 26 stateful · 2026-09-19 20:28:45 UTC
Parallelism
67/100
Blocked
73%
Avg conflicts / tx
2.33
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,272,539 · 27 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w17w211w112w213w314w415w516w617w618w719w824w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0fc536fb…1aa1
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x7c2ad520…3329
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0028
0x1b6862…e19c
8 touches
6 conflicts
0x91945265…e58b
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x141af414…18e0
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
28 conflicts on slot 0x0fc536fb1f…c81aa1
Audit this contract →
← previous block·next block →recent activity