← previous blocknext block →recent activity
Analyzing
Block #106,934,590
20 transactions · 20 stateful · 2026-09-22 04:01:50 UTC
Parallelism
65/100
Blocked
45%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,934,590 · 20 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
1w02w13w25w06w18w09w111w212w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e58deff…c5d0
0x34b655…2a6f
12 touches
15 conflicts
0xdfac0724…d23e
0x34b655…2a6f
10 touches
10 conflicts
0xccebf5c5…8758
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x8590b692…b267
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0xd5b10148…e636
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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 0x4e58deff76…56c5d0
Audit this contract →
← previous block·next block →recent activity