← previous blocknext block →recent activity
Analyzing
Block #105,869,384
26 transactions · 25 stateful · 2026-09-18 10:38:37 UTC
Parallelism
77/100
Blocked
40%
Avg conflicts / tx
0.69
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,869,384 · 26 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
1w02w13w25w06w113w114w215w216w317w418w523w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8063b7e8…32fd
0x34b655…2a6f
10 touches
10 conflicts
0x23529e13…6f25
0x34b655…2a6f
10 touches
10 conflicts
0x329f9fde…fe9c
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd0ec60a1…d240
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
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
10 conflicts on slot 0x8063b7e8d0…ce32fd
Audit this contract →
← previous block·next block →recent activity