← previous blocknext block →recent activity
Analyzing
Block #105,870,065
31 transactions · 25 stateful · 2026-09-18 10:42:03 UTC
Parallelism
71/100
Blocked
44%
Avg conflicts / tx
1.03
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #105,870,065 · 31 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
5w06w07w111w117w018w119w220w321w422w523w624w725w830w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6a49d87d…b106
0x34b655…2a6f
12 touches
15 conflicts
0x89999c15…fdac
0x34b655…2a6f
10 touches
10 conflicts
0x9dccd2a9…2790
0x34b655…2a6f
10 touches
10 conflicts
0x0efc210e…70ab
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xcc844ab5…4c6d
0x34b655…2a6f
8 touches
6 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
15 conflicts on slot 0x6a49d87dc4…ecb106
Audit this contract →
← previous block·next block →recent activity