← previous blocknext block →recent activity
Analyzing
Block #104,023,767
21 transactions · 19 stateful · 2026-09-11 23:15:20 UTC
Parallelism
62/100
Blocked
53%
Avg conflicts / tx
1.57
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #104,023,767 · 21 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
1w02w13w25w06w19w010w111w212w314w415w519w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x61ca6437…2142
0x34b655…2a6f
16 touches
28 conflicts
0x7211ade0…c8c6
0x34b655…2a6f
14 touches
21 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0xdf871c2a…17b3
0x34b655…2a6f
12 touches
15 conflicts
0x0bf19f18…c22c
0x34b655…2a6f
12 touches
15 conflicts
0x1a69c7c5…09cc
0x34b655…2a6f
12 touches
15 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
28 conflicts on slot 0x61ca6437ec…412142
Audit this contract →
← previous block·next block →recent activity