← previous blocknext block →recent activity
Analyzing
Block #104,024,566
15 transactions · 15 stateful · 2026-09-11 23:19:24 UTC
Parallelism
47/100
Blocked
47%
Avg conflicts / tx
1.87
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #104,024,566 · 15 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
3w04w15w26w37w48w59w610w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c68c214…1b34
0x34b655…2a6f
16 touches
28 conflicts
0x61ca6437…2142
0x34b655…2a6f
16 touches
28 conflicts
0xa4f6516c…aad0
0x34b655…2a6f
14 touches
21 conflicts
0xf1595b25…ef40
0x34b655…2a6f
14 touches
21 conflicts
0x49890ced…6f23
0x34b655…2a6f
14 touches
21 conflicts
0xc7954a60…d294
0x34b655…2a6f
14 touches
21 conflicts
0x949fc5d9…55f3
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…002b
0x1b6862…e19c
2 touches
0 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
28 conflicts on slot 0x3c68c21456…dd1b34
Audit this contract →
← previous block·next block →recent activity