← previous blocknext block →recent activity
Analyzing
Block #105,931,505
28 transactions · 27 stateful · 2026-09-18 15:52:10 UTC
Parallelism
71/100
Blocked
48%
Avg conflicts / tx
1.5
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,931,505 · 28 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w310w413w119w323w524w627w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x375b6201…9c1e
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc567b9f3…bfd2
0x34b655…2a6f
8 touches
6 conflicts
0xee0147b7…9b9c
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x6d89ee77…72bf
0x34b655…2a6f
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 0x375b620113…4b9c1e
Audit this contract →
← previous block·next block →recent activity