← previous blocknext block →recent activity
Analyzing
Block #106,954,524
25 transactions · 21 stateful · 2026-09-22 05:42:11 UTC
Parallelism
60/100
Blocked
57%
Avg conflicts / tx
1.92
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,954,524 · 25 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w17w29w010w311w412w518w619w720w821w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c26d635…1bbf
0x34b655…2a6f
16 touches
28 conflicts
0x01ad5dd0…11a1
0x34b655…2a6f
10 touches
10 conflicts
0x70986451…c6bd
0x34b655…2a6f
10 touches
10 conflicts
0x9951edbd…d218
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xf179a759…054e
0x34b655…2a6f
10 touches
10 conflicts
0x2bedfb26…8b9b
0x34b655…2a6f
10 touches
10 conflicts
0xd9a74048…63af
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
28 conflicts on slot 0x6c26d63540…461bbf
Audit this contract →
← previous block·next block →recent activity