← previous blocknext block →recent activity
Analyzing
Block #106,189,164
33 transactions · 31 stateful · 2026-09-19 13:29:03 UTC
Parallelism
79/100
Blocked
58%
Avg conflicts / tx
1.27
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,189,164 · 33 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
1w02w13w24w35w46w47w08w211w012w113w018w119w220w321w423w324w426w631w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfefb0189…f726
0x34b655…2a6f
10 touches
10 conflicts
0x0f0c28ff…c887
0xd32edf…ff58
9 touches
10 conflicts
0x8fcbf9b2…a36e
0x34b655…2a6f
8 touches
6 conflicts
0x0f28fb99…3d2f
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xec2a8d79…70cb
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
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
10 conflicts on slot 0xfefb01895a…9bf726
Audit this contract →
← previous block·next block →recent activity