← previous blocknext block →recent activity
Analyzing
Block #104,032,312
21 transactions · 20 stateful · 2026-09-11 23:58:40 UTC
Parallelism
52/100
Blocked
60%
Avg conflicts / tx
2.33
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #104,032,312 · 21 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
1w02w13w24w36w07w18w29w310w411w512w613w714w817w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ddfdaf2…9e00
0x34b655…2a6f
20 touches
45 conflicts
0x68e5627d…6f8f
0x34b655…2a6f
20 touches
45 conflicts
0x028594e3…157c
0x34b655…2a6f
20 touches
45 conflicts
0x49890ced…6f23
0x34b655…2a6f
18 touches
36 conflicts
0x6f4e7625…aba5
0x34b655…2a6f
18 touches
36 conflicts
0x1e7c9ff8…0fa3
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
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
45 conflicts on slot 0x0ddfdaf2af…269e00
Audit this contract →
← previous block·next block →recent activity