← previous blocknext block →recent activity
Analyzing
Block #105,600,310
17 transactions · 14 stateful · 2026-09-17 12:02:52 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,600,310 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w17w28w312w313w416w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81ca8c9e…28cb
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x3f03e5f9…2c7a
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc948dbdc…199a
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x178a61ad…4958
0x34b655…2a6f
4 touches
1 conflict
0xb2560305…f27d
0x34b655…2a6f
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 0x81ca8c9e47…f128cb
Audit this contract →
← previous block·next block →recent activity