← previous blocknext block →recent activity
Analyzing
Block #105,869,147
25 transactions · 23 stateful · 2026-09-18 10:37:26 UTC
Parallelism
72/100
Blocked
52%
Avg conflicts / tx
1.2
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,869,147 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w39w010w011w114w215w316w417w518w622w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1deb89a5…e7c6
0x34b655…2a6f
14 touches
21 conflicts
0x23529e13…6f25
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x18978822…2623
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…004c
0x80c745…7210
8 touches
6 conflicts
0xd911522b…e960
0x34b655…2a6f
6 touches
3 conflicts
0xf2bbd8fc…7e49
0x34b655…2a6f
6 touches
3 conflicts
0x80398c66…f3cc
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
21 conflicts on slot 0x1deb89a502…78e7c6
Audit this contract →
← previous block·next block →recent activity