← previous blocknext block →recent activity
Analyzing
Block #105,460,795
20 transactions · 18 stateful · 2026-09-17 00:20:44 UTC
Parallelism
80/100
Blocked
39%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,460,795 · 20 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
1w03w15w06w07w112w213w114w215w317w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x178a61ad…4958
0x34b655…2a6f
6 touches
3 conflicts
0xf1d04e14…2040
0x34b655…2a6f
6 touches
3 conflicts
0xc5847c4d…a65c
0x34b655…2a6f
6 touches
3 conflicts
0xa5811d93…8c73
0x34b655…2a6f
6 touches
3 conflicts
0x5f34739b…14fd
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x33848157…61dc
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
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
3 conflicts on slot 0x178a61ad8a…8c4958
Audit this contract →
← previous block·next block →recent activity