← previous blocknext block →recent activity
Analyzing
Block #104,165,153
24 transactions · 24 stateful · 2026-09-12 11:14:38 UTC
Parallelism
63/100
Blocked
54%
Avg conflicts / tx
1.92
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #104,165,153 · 24 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w48w29w517w618w719w820w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23f382f2…f742
0x34b655…2a6f
14 touches
21 conflicts
0x705a9a1a…db08
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xef1de905…0582
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x1bb56de3…732e
0x34b655…2a6f
8 touches
6 conflicts
0x6b89ce6f…cc35
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
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 0x23f382f21f…8df742
Audit this contract →
← previous block·next block →recent activity