← previous blocknext block →recent activity
Analyzing
Block #106,207,714
36 transactions · 32 stateful · 2026-09-19 15:02:27 UTC
Parallelism
81/100
Blocked
66%
Avg conflicts / tx
1.44
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,207,714 · 36 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
1w02w13w24w35w06w17w210w214w428w329w330w431w532w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85332e39…0222
0x34b655…2a6f
12 touches
15 conflicts
0xd17580f9…ece1
0x754704…b603
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0xd53220ed…473b
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x15e313f3…9aa1
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
15 conflicts on slot 0x85332e39ec…770222
Audit this contract →
← previous block·next block →recent activity