← previous blocknext block →recent activity
Analyzing
Block #102,809,354
51 transactions · 43 stateful · 2026-09-07 17:10:04 UTC
Parallelism
74/100
Blocked
67%
Avg conflicts / tx
2.08
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #102,809,354 · 51 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w836w1141w642w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
18 touches
36 conflicts
0xadf6dcbd…0f7b
0xd32edf…ff58
17 touches
36 conflicts
0x3b9a3d0c…0df6
0x40c49f…2af0
17 touches
36 conflicts
0x485d2778…aa5d
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…001b
0x1b6862…e19c
14 touches
21 conflicts
0xa1087a5c…66c4
0x754704…b603
14 touches
21 conflicts
0x00000000…002b
0x1b6862…e19c
14 touches
21 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
36 conflicts on slot 0x002fed350f…7379fa
Audit this contract →
← previous block·next block →recent activity