← previous blocknext block →recent activity
Analyzing
Block #105,460,721
22 transactions · 20 stateful · 2026-09-17 00:20:22 UTC
Parallelism
73/100
Blocked
55%
Avg conflicts / tx
1.18
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,460,721 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w07w28w312w113w214w315w316w419w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdf5f067e…8786
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb80
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xdf5f067e5e…758786
Audit this contract →
← previous block·next block →recent activity