← previous blocknext block →recent activity
Analyzing
Block #106,953,341
42 transactions · 39 stateful · 2026-09-22 05:36:14 UTC
Parallelism
62/100
Blocked
74%
Avg conflicts / tx
2.9
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #106,953,341 · 42 txs across 16 waves · depth 16
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
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w19w010w414w015w116w217w318w123w225w826w328w430w931w1033w1234w1335w1436w1538w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x693575b5…22a8
0x34b655…2a6f
22 touches
55 conflicts
0x23769ebc…c8ed
0x34b655…2a6f
16 touches
28 conflicts
0x148c2efc…4410
0x34b655…2a6f
16 touches
28 conflicts
0x941bd594…21fd
0x34b655…2a6f
14 touches
21 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
14 touches
21 conflicts
0xc53799eb…d928
0x34b655…2a6f
14 touches
21 conflicts
0x91bb1d81…820e
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 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
55 conflicts on slot 0x693575b593…9d22a8
Audit this contract →
← previous block·next block →recent activity