← previous blocknext block →recent activity
Analyzing
Block #106,555,325
17 transactions · 17 stateful · 2026-09-20 20:11:57 UTC
Parallelism
59/100
Blocked
53%
Avg conflicts / tx
1.53
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,555,325 · 17 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
1w02w16w07w28w39w411w312w413w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x03a6ea2e…2b49
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…001e
0x1b6862…e19c
10 touches
10 conflicts
0xa35509fa…5cb3
0x34b655…2a6f
10 touches
10 conflicts
0xcb45d9d6…cb86
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x1188b655…669d
0xd32edf…ff58
9 touches
10 conflicts
0xc53799eb…d928
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0x03a6ea2ef2…442b49
Audit this contract →
← previous block·next block →recent activity