← previous blocknext block →recent activity
Analyzing
Block #105,931,311
25 transactions · 24 stateful · 2026-09-18 15:51:11 UTC
Parallelism
60/100
Blocked
79%
Avg conflicts / tx
2.44
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #105,931,311 · 25 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w07w110w213w314w415w516w617w718w819w921w324w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
14 touches
21 conflicts
0xdb11940a…519b
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0019
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0029
0x1b6862…e19c
10 touches
10 conflicts
0x0a6cb118…4ca4
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x07bb3f5a…617e
0x34b655…2a6f
10 touches
10 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