← previous blocknext block →recent activity
Analyzing
Block #105,932,177
25 transactions · 23 stateful · 2026-09-18 15:55:33 UTC
Parallelism
68/100
Blocked
57%
Avg conflicts / tx
1.6
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #105,932,177 · 25 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
1w02w13w04w16w07w18w213w114w216w317w418w519w620w723w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe796f8b7…ad55
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xf195ad96…e0c3
0x34b655…2a6f
8 touches
6 conflicts
0x6a23a951…2791
0x34b655…2a6f
8 touches
6 conflicts
0x7c989dc1…a3e8
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x1d904501…8f0a
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 0xe796f8b7af…c7ad55
Audit this contract →
← previous block·next block →recent activity