← previous blocknext block →recent activity
Analyzing
Block #106,185,658
23 transactions · 20 stateful · 2026-09-19 13:11:24 UTC
Parallelism
70/100
Blocked
70%
Avg conflicts / tx
1.7
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,185,658 · 23 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
1w02w13w24w35w18w411w212w313w414w415w516w622w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x000bde1a…e123
0x34b655…2a6f
14 touches
21 conflicts
0x42260953…76b3
0x34b655…2a6f
10 touches
10 conflicts
0x1bde6d79…2d4f
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…001e
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
8 touches
6 conflicts
0x59658b83…222b
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
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
21 conflicts on slot 0x000bde1afc…91e123
Audit this contract →
← previous block·next block →recent activity