← previous blocknext block →recent activity
Analyzing
Block #106,420,860
22 transactions · 22 stateful · 2026-09-20 08:55:09 UTC
Parallelism
59/100
Blocked
55%
Avg conflicts / tx
1.5
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,420,860 · 22 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
1w02w13w24w35w36w411w312w417w518w519w620w721w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5c53705…ea66
0x34b655…2a6f
14 touches
21 conflicts
0xa60eabc0…9f8c
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xe5060fe3…ebe6
0x1b6862…e19c
8 touches
6 conflicts
0x310a7246…2dcb
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
21 conflicts on slot 0xb5c53705ff…f6ea66
Audit this contract →
← previous block·next block →recent activity