← previous blocknext block →recent activity
Analyzing
Block #102,104,614
35 transactions · 32 stateful · 2026-09-05 05:42:14 UTC
Parallelism
71/100
Blocked
59%
Avg conflicts / tx
1.6
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #102,104,614 · 35 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
1w02w13w24w35w47w58w69w710w814w819w120w130w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
14 touches
21 conflicts
0x00000000…003d
0x065c9d…c394
14 touches
21 conflicts
0x77ed432f…fa04
0x065c9d…c394
12 touches
15 conflicts
0x95523e2a…4c01
0x065c9d…c394
12 touches
15 conflicts
0x00000000…001c
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002c
0x1b6862…e19c
10 touches
10 conflicts
0xd53220ed…4738
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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: Kuru Exchange: MarginAccount
21 conflicts on slot 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity