← previous blocknext block →recent activity
Analyzing
Block #106,932,155
26 transactions · 25 stateful · 2026-09-22 03:49:35 UTC
Parallelism
62/100
Blocked
64%
Avg conflicts / tx
2.04
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,932,155 · 26 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w27w49w310w411w513w415w620w321w722w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec25545e…589b
0x34b655…2a6f
14 touches
21 conflicts
0x94e7f277…471b
0x34b655…2a6f
12 touches
15 conflicts
0x70986451…c6bd
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…001d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002d
0x1b6862…e19c
10 touches
10 conflicts
0xba5743c7…21c4
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x251ee419…4404
0x34b655…2a6f
10 touches
10 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
21 conflicts on slot 0xec25545ed8…c1589b
Audit this contract →
← previous block·next block →recent activity