← previous blocknext block →recent activity
Analyzing
Block #104,148,192
22 transactions · 20 stateful · 2026-09-12 09:48:26 UTC
Parallelism
55/100
Blocked
65%
Avg conflicts / tx
2.27
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #104,148,192 · 22 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
1w02w13w24w35w16w27w311w415w517w618w719w820w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0x344ba98e…d204
0x34b655…2a6f
16 touches
28 conflicts
0xd66696e0…0842
0x34b655…2a6f
12 touches
15 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
12 touches
15 conflicts
0xc1998045…f700
0x34b655…2a6f
10 touches
10 conflicts
0x6183ee9a…21b1
0x34b655…2a6f
10 touches
10 conflicts
0x705a9a1a…db08
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
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
36 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity