← previous blocknext block →recent activity
Analyzing
Block #105,642,730
20 transactions · 19 stateful · 2026-09-17 15:36:27 UTC
Parallelism
80/100
Blocked
37%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,642,730 · 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
1w02w03w15w06w18w013w214w116w217w319w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a6ce689…7b8a
0x34b655…2a6f
8 touches
6 conflicts
0xd99d25df…ecd8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x4118bd12…924a
0x34b655…2a6f
4 touches
1 conflict
0x52c6ef89…8e97
0x34b655…2a6f
4 touches
1 conflict
0x86bd79a5…1f48
0x34b655…2a6f
4 touches
1 conflict
0xb9fe324c…70c7
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 0x9a6ce689f5…747b8a
Audit this contract →
← previous block·next block →recent activity