← previous blocknext block →recent activity
Analyzing
Block #106,924,074
49 transactions · 43 stateful · 2026-09-22 03:08:54 UTC
Parallelism
65/100
Blocked
67%
Avg conflicts / tx
2.49
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #106,924,074 · 49 txs across 17 waves · depth 17
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
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w017w118w224w825w926w1027w1128w1229w1330w1440w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46483cb1…e7ca
0x34b655…2a6f
22 touches
55 conflicts
0xc8c615d4…5da3
0x34b655…2a6f
20 touches
45 conflicts
0xccebf5c5…8758
0x34b655…2a6f
18 touches
36 conflicts
0x9a339ea4…3cd6
0x34b655…2a6f
18 touches
36 conflicts
0x49890ced…6f23
0x34b655…2a6f
14 touches
21 conflicts
0x8e879690…725e
0x34b655…2a6f
14 touches
21 conflicts
0xfa324e43…8899
0x1b6862…e19c
12 touches
15 conflicts
0x2d2b9df3…2450
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 0x46483cb14f…c1e7ca
Audit this contract →
← previous block·next block →recent activity