← previous blocknext block →recent activity
Analyzing
Block #105,749,211
23 transactions · 23 stateful · 2026-09-18 00:32:22 UTC
Parallelism
48/100
Blocked
65%
Avg conflicts / tx
2.96
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #105,749,211 · 23 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w410w512w213w514w615w716w817w918w1019w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
14 touches
21 conflicts
0x594dc2f3…30a9
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x213b816c…a5e0
0x34b655…2a6f
12 touches
15 conflicts
0x1943f5ca…efda
0x34b655…2a6f
10 touches
10 conflicts
0x43e3decb…be40
0x34b655…2a6f
10 touches
10 conflicts
0xf90c6521…d8f0
0x34b655…2a6f
8 touches
6 conflicts
0xdaf02dea…dbd8
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
21 conflicts on slot 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity