← previous blocknext block →recent activity
Analyzing
Block #106,924,258
33 transactions · 31 stateful · 2026-09-22 03:09:50 UTC
Parallelism
55/100
Blocked
71%
Avg conflicts / tx
2.42
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #106,924,258 · 33 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w010w312w013w114w215w316w417w518w619w720w821w922w1023w1124w1229w130w431w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x574628e9…dcc3
0x34b655…2a6f
20 touches
45 conflicts
0xc7b7704f…ab36
0x34b655…2a6f
18 touches
36 conflicts
0xccebf5c5…8758
0x34b655…2a6f
18 touches
36 conflicts
0xd192f4ed…d7ec
0x34b655…2a6f
14 touches
21 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0x4ff73652…74f7
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0x0f28fb99…3d2e
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
45 conflicts on slot 0x574628e919…e4dcc3
Audit this contract →
← previous block·next block →recent activity