← previous blocknext block →recent activity
Analyzing
Block #104,196,163
26 transactions · 24 stateful · 2026-09-12 13:51:57 UTC
Parallelism
62/100
Blocked
58%
Avg conflicts / tx
1.54
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #104,196,163 · 26 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
1w03w04w15w26w37w39w313w314w119w420w421w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2bea5ce8…3c07
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x5d6da397…6c5c
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641d
0x34b655…2a6f
6 touches
3 conflicts
0x70a7b5d6…fe0e
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 0x2bea5ce899…543c07
Audit this contract →
← previous block·next block →recent activity