← previous blocknext block →recent activity
Analyzing
Block #104,204,535
15 transactions · 14 stateful · 2026-09-12 14:34:32 UTC
Parallelism
60/100
Blocked
50%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #104,204,535 · 15 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w17w08w19w210w311w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3d287a5a…c144
0x34b655…2a6f
12 touches
15 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xf61165ef…adb9
0x34b655…2a6f
10 touches
10 conflicts
0x70a7b5d6…fe0e
0x34b655…2a6f
8 touches
6 conflicts
0xcb0221be…c2b3
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x0deb5804…40c6
0x34b655…2a6f
4 touches
1 conflict
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
15 conflicts on slot 0x3d287a5aea…23c144
Audit this contract →
← previous block·next block →recent activity