← previous blocknext block →recent activity
Analyzing
Block #105,843,997
26 transactions · 24 stateful · 2026-09-18 08:30:50 UTC
Parallelism
73/100
Blocked
54%
Avg conflicts / tx
1.27
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,843,997 · 26 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
1w02w13w24w35w46w016w017w118w119w220w321w422w423w525w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a548af5…0eb0
0x34b655…2a6f
12 touches
15 conflicts
0x27e92642…b1c1
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xf13f879f…3904
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0x083a8763…5a7f
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x3aed8a17…20f9
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
15 conflicts on slot 0x5a548af508…f00eb0
Audit this contract →
← previous block·next block →recent activity