← previous blocknext block →recent activity
Analyzing
Block #105,582,706
19 transactions · 17 stateful · 2026-09-17 10:34:16 UTC
Parallelism
58/100
Blocked
65%
Avg conflicts / tx
1.42
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,582,706 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w27w08w39w210w213w314w415w516w617w718w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x134b4621…c07d
0x34b655…2a6f
14 touches
21 conflicts
0x89999c15…fdac
0x34b655…2a6f
10 touches
10 conflicts
0x7b42f6a7…f49c
0x34b655…2a6f
8 touches
6 conflicts
0x2d3930d3…c9b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0x3e04662b…0da3
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
21 conflicts on slot 0x134b4621f8…b7c07d
Audit this contract →
← previous block·next block →recent activity