← previous blocknext block →recent activity
Analyzing
Block #105,626,168
80 transactions · 50 stateful · 2026-09-17 14:13:04 UTC
Parallelism
77/100
Blocked
64%
Avg conflicts / tx
1.77
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #105,626,168 · 80 txs across 18 waves · depth 18
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
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w28w39w415w017w118w224w325w426w542w643w744w846w947w1062w563w664w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
24 touches
66 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x9c6a9da2…c628
0x34b655…2a6f
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
10 touches
10 conflicts
0x1eb0fab5…3517
0x34b655…2a6f
8 touches
6 conflicts
0x3347cbe5…846c
0x34b655…2a6f
8 touches
6 conflicts
0x3cfe4586…0bd9
0x34b655…2a6f
8 touches
6 conflicts
0x62d6e82b…a750
0x34b655…2a6f
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
66 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity