← previous blocknext block →recent activity
Analyzing
Block #106,931,190
25 transactions · 23 stateful · 2026-09-22 03:44:43 UTC
Parallelism
72/100
Blocked
70%
Avg conflicts / tx
1.96
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,931,190 · 25 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
1w02w13w24w37w08w19w210w311w412w513w623w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c26d635…1bbf
0x34b655…2a6f
14 touches
21 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
14 touches
21 conflicts
0xba1edffb…323e
0x34b655…2a6f
14 touches
21 conflicts
0x3780a34a…b50a
0x34b655…2a6f
14 touches
21 conflicts
0x48f91335…a89c
0x34b655…2a6f
14 touches
21 conflicts
0x49890ced…6f23
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
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 0x6c26d63540…461bbf
Audit this contract →
← previous block·next block →recent activity