← previous blocknext block →recent activity
Analyzing
Block #105,844,615
25 transactions · 25 stateful · 2026-09-18 08:33:56 UTC
Parallelism
76/100
Blocked
56%
Avg conflicts / tx
1.36
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,844,615 · 25 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
1w02w13w24w35w46w08w110w414w215w316w417w524w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x83ec1322…c4ad
0x34b655…2a6f
12 touches
15 conflicts
0xdfce7dfe…5053
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xa57a1425…d413
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0xd5b10148…e638
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xca841faa…486a
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 0x83ec1322bb…5dc4ad
Audit this contract →
← previous block·next block →recent activity