← previous blocknext block →recent activity
Analyzing
Block #106,464,325
30 transactions · 29 stateful · 2026-09-20 12:33:58 UTC
Parallelism
53/100
Blocked
52%
Avg conflicts / tx
2.57
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #106,464,325 · 30 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w48w59w612w715w816w917w1018w1119w1220w1329w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x54563e2b…7469
0x34b655…2a6f
24 touches
66 conflicts
0xd563f3a1…94b1
0x34b655…2a6f
20 touches
45 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x5655f5c3…6b75
0x34b655…2a6f
10 touches
10 conflicts
0x524f0872…0d12
0x34b655…2a6f
10 touches
10 conflicts
0x232b0b19…d946
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x1b25f260…c429
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
66 conflicts on slot 0x54563e2be8…237469
Audit this contract →
← previous block·next block →recent activity