← previous blocknext block →recent activity
Analyzing
Block #105,470,711
17 transactions · 17 stateful · 2026-09-17 01:10:38 UTC
Parallelism
76/100
Blocked
24%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,470,711 · 17 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
1w03w15w07w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc16f6da7…5399
0x34b655…2a6f
8 touches
6 conflicts
0xe66b5bc0…a209
0x34b655…2a6f
6 touches
3 conflicts
0x5b6af007…0f35
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xc65ff65a…2dfd
0x34b655…2a6f
4 touches
1 conflict
0x7c51d9aa…af39
0x34b655…2a6f
4 touches
1 conflict
0x07147649…d859
0x34b655…2a6f
4 touches
1 conflict
0x62811193…1868
0x34ae4d…3fc5
2 touches
0 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
6 conflicts on slot 0xc16f6da7d4…f75399
Audit this contract →
← previous block·next block →recent activity