← previous blocknext block →recent activity
Analyzing
Block #105,852,391
30 transactions · 27 stateful · 2026-09-18 09:13:06 UTC
Parallelism
70/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #105,852,391 · 30 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w514w117w018w419w520w621w622w723w828w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f0befc9…48e9
0x34b655…2a6f
10 touches
10 conflicts
0x55192654…91fe
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0xba5743c7…21c6
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
10 conflicts on slot 0x6f0befc9d9…4248e9
Audit this contract →
← previous block·next block →recent activity