← previous blocknext block →recent activity
Analyzing
Block #106,575,877
22 transactions · 22 stateful · 2026-09-20 21:55:23 UTC
Parallelism
68/100
Blocked
59%
Avg conflicts / tx
1.41
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,575,877 · 22 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
1w02w13w24w05w16w08w19w310w013w114w115w216w317w418w519w621w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe77107b6…426b
0x34b655…2a6f
14 touches
21 conflicts
0x31d88d27…7617
0x34b655…2a6f
8 touches
6 conflicts
0x2e5e06ed…780e
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0x4e7eb462…b2b0
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x159cff26…7665
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
21 conflicts on slot 0xe77107b68d…10426b
Audit this contract →
← previous block·next block →recent activity