← previous blocknext block →recent activity
Analyzing
Block #105,853,456
32 transactions · 31 stateful · 2026-09-18 09:18:27 UTC
Parallelism
75/100
Blocked
45%
Avg conflicts / tx
1.19
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,853,456 · 32 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
1w02w13w24w35w015w317w418w519w620w721w122w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a6070ec…08c3
0x34b655…2a6f
14 touches
21 conflicts
0xfefb0189…f726
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x831f75b4…945d
0x34b655…2a6f
8 touches
6 conflicts
0x14d1bf0e…e0a0
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
21 conflicts on slot 0x3a6070ec5f…2c08c3
Audit this contract →
← previous block·next block →recent activity