← previous blocknext block →recent activity
Analyzing
Block #104,203,952
24 transactions · 21 stateful · 2026-09-12 14:31:34 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
1.17
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #104,203,952 · 24 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
1w02w17w28w310w411w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9d9f3717…44e7
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x7de57974…f5ba
0x34b655…2a6f
10 touches
10 conflicts
0xf3a5636c…14e8
0x34b655…2a6f
10 touches
10 conflicts
0x15ae3bf3…2507
0x34b655…2a6f
10 touches
10 conflicts
0x2b635ea7…4c03
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0xa7481e1f…531f
0x34b655…2a6f
8 touches
6 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 0x9d9f371782…a844e7
Audit this contract →
← previous block·next block →recent activity