← previous blocknext block →recent activity
Analyzing
Block #105,618,923
19 transactions · 17 stateful · 2026-09-17 13:36:35 UTC
Parallelism
79/100
Blocked
53%
Avg conflicts / tx
0.74
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,618,923 · 19 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
1w04w15w26w07w18w212w213w315w316w317w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0xc73fd549…2e28
0x851145…3f07
6 touches
3 conflicts
0x1a79e9de…99e6
0x851145…3f07
6 touches
3 conflicts
0xe84e88e5…aabf
0x34b655…2a6f
4 touches
1 conflict
0xf61a04b5…0753
0x34b655…2a6f
4 touches
1 conflict
0x9afdb944…06bd
0x37db7f…ec7b
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity