← previous blocknext block →recent activity
Analyzing
Block #104,199,182
29 transactions · 24 stateful · 2026-09-12 14:07:17 UTC
Parallelism
66/100
Blocked
63%
Avg conflicts / tx
1.69
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #104,199,182 · 29 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
1w02w13w25w36w410w513w119w620w721w822w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ccfe55c…de03
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xd66696e0…0842
0x34b655…2a6f
12 touches
15 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
12 touches
15 conflicts
0x02ed4afa…b107
0x34b655…2a6f
8 touches
6 conflicts
0x08cc68a2…2a59
0x34b655…2a6f
8 touches
6 conflicts
0x11fd16e3…c46f
0x34b655…2a6f
8 touches
6 conflicts
0x15a8300c…162d
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
28 conflicts on slot 0x4ccfe55c0b…fbde03
Audit this contract →
← previous block·next block →recent activity