← previous blocknext block →recent activity
Analyzing
Block #105,403,321
26 transactions · 24 stateful · 2026-09-16 19:31:28 UTC
Parallelism
58/100
Blocked
46%
Avg conflicts / tx
1.69
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #105,403,321 · 26 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w08w19w210w311w414w515w622w723w824w925w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x100812e9…12b7
0x34b655…2a6f
14 touches
21 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0xf64b5ee4…93c0
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…002e
0x1b6862…e19c
10 touches
10 conflicts
0x4e7eb462…b2b0
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 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 0x100812e99b…9e12b7
Audit this contract →
← previous block·next block →recent activity