← previous blocknext block →recent activity
Analyzing
Block #105,856,106
33 transactions · 29 stateful · 2026-09-18 09:31:48 UTC
Parallelism
79/100
Blocked
59%
Avg conflicts / tx
1.12
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,856,106 · 33 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w17w28w39w410w511w415w421w525w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x97e4c862…4419
0x34b655…2a6f
12 touches
15 conflicts
0xba1edffb…323e
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0018
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0028
0x1b6862…e19c
8 touches
6 conflicts
0xfefb0189…f726
0x34b655…2a6f
8 touches
6 conflicts
0x6d43ee99…bdd3
0x1b6862…e19c
8 touches
6 conflicts
0xab981df1…2941
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0012
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
15 conflicts on slot 0x97e4c86258…af4419
Audit this contract →
← previous block·next block →recent activity