← previous blocknext block →recent activity
Analyzing
Block #105,582,708
29 transactions · 27 stateful · 2026-09-17 10:34:17 UTC
Parallelism
79/100
Blocked
48%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,582,708 · 29 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
2w03w04w06w07w18w29w010w111w112w114w115w216w218w319w420w421w522w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x134b4621…c07d
0x34b655…2a6f
10 touches
10 conflicts
0xd35bb5ac…3586
0x065c9d…c394
6 touches
3 conflicts
0x2d3930d3…c9b8
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7b42f6a7…f49c
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
10 conflicts on slot 0x134b4621f8…b7c07d
Audit this contract →
← previous block·next block →recent activity