← previous blocknext block →recent activity
Analyzing
Block #105,853,392
20 transactions · 19 stateful · 2026-09-18 09:18:08 UTC
Parallelism
60/100
Blocked
58%
Avg conflicts / tx
1.65
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,853,392 · 20 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
1w02w13w04w15w26w37w48w59w610w711w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6caf33e2…c261
0x34b655…2a6f
16 touches
28 conflicts
0x7c51d9aa…af39
0x34b655…2a6f
10 touches
10 conflicts
0xd6d040d9…9ae3
0x34b655…2a6f
10 touches
10 conflicts
0x74a21ae3…38f9
0x34b655…2a6f
8 touches
6 conflicts
0x56a78e60…72fb
0x34b655…2a6f
8 touches
6 conflicts
0x29169c83…348a
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
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
28 conflicts on slot 0x6caf33e26f…3dc261
Audit this contract →
← previous block·next block →recent activity