← previous blocknext block →recent activity
Analyzing
Block #105,925,247
27 transactions · 25 stateful · 2026-09-18 15:20:40 UTC
Parallelism
59/100
Blocked
60%
Avg conflicts / tx
1.81
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #105,925,247 · 27 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
1w02w13w24w35w46w27w312w514w221w622w725w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf537d3a9…730b
0x34b655…2a6f
14 touches
21 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0019
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0029
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xdb95e18e…c738
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
21 conflicts on slot 0xf537d3a965…67730b
Audit this contract →
← previous block·next block →recent activity