← previous blocknext block →recent activity
Analyzing
Block #106,924,326
26 transactions · 26 stateful · 2026-09-22 03:10:11 UTC
Parallelism
69/100
Blocked
69%
Avg conflicts / tx
1.77
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,924,326 · 26 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w19w010w111w212w313w414w515w616w717w318w419w223w325w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94e7f277…471b
0x34b655…2a6f
16 touches
28 conflicts
0xe06d2b07…cdd0
0x34b655…2a6f
16 touches
28 conflicts
0xccebf5c5…8758
0x34b655…2a6f
16 touches
28 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0x58e06bab…34d0
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xc824469a…6425
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
28 conflicts on slot 0x94e7f27794…c6471b
Audit this contract →
← previous block·next block →recent activity