← previous blocknext block →recent activity
Analyzing
Block #105,619,263
33 transactions · 26 stateful · 2026-09-17 13:38:18 UTC
Parallelism
73/100
Blocked
62%
Avg conflicts / tx
1.24
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #105,619,263 · 33 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w18w214w116w317w418w519w620w723w324w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
16 touches
28 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x77882bab…8eda
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xe84e88e5…aabf
0x34b655…2a6f
6 touches
3 conflicts
0xedee7e09…6888
0x34b655…2a6f
6 touches
3 conflicts
0x9afdb944…06bd
0x37db7f…ec7b
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
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
28 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity