← previous blocknext block →recent activity
Analyzing
Block #105,846,124
20 transactions · 20 stateful · 2026-09-18 08:41:34 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,846,124 · 20 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
1w03w04w15w06w17w19w213w214w315w416w518w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08731834…6415
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x75d5f8d3…f860
0x34b655…2a6f
6 touches
3 conflicts
0xdd6538fb…2b3f
0x34b655…2a6f
4 touches
1 conflict
0x941bd594…21fd
0x34b655…2a6f
4 touches
1 conflict
0x9ff4ca89…6115
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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
6 conflicts on slot 0x087318341f…516415
Audit this contract →
← previous block·next block →recent activity