← previous blocknext block →recent activity
Analyzing
Block #104,160,283
17 transactions · 17 stateful · 2026-09-12 10:49:56 UTC
Parallelism
71/100
Blocked
53%
Avg conflicts / tx
1.24
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #104,160,283 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w07w08w111w112w213w314w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a2055c7…9054
0x34b655…2a6f
10 touches
10 conflicts
0x33649c4f…b327
0x34b655…2a6f
10 touches
10 conflicts
0x640c4fb2…044a
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0xf952cd9e…ea58
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…641e
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…641f
0x34b655…2a6f
10 touches
10 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
10 conflicts on slot 0x1a2055c785…e29054
Audit this contract →
← previous block·next block →recent activity