← previous blocknext block →recent activity
Analyzing
Block #105,856,467
23 transactions · 21 stateful · 2026-09-18 09:33:37 UTC
Parallelism
83/100
Blocked
48%
Avg conflicts / tx
0.74
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,856,467 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w314w116w217w218w019w120w221w322w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x29f17906…74cf
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x297de2d5…7396
0x34b655…2a6f
8 touches
6 conflicts
0x5c48eea2…5491
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 conflicts
0xada193dc…5c79
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x184a9b09…c825
0x34b655…2a6f
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
6 conflicts on slot 0x29f17906ee…bd74cf
Audit this contract →
← previous block·next block →recent activity