← previous blocknext block →recent activity
Analyzing
Block #102,810,113
25 transactions · 22 stateful · 2026-09-07 17:13:55 UTC
Parallelism
64/100
Blocked
55%
Avg conflicts / tx
1.28
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #102,810,113 · 25 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
1w02w13w24w39w212w313w414w515w616w718w123w824w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6518075e…2b17
0x2a68ba…90c5
14 touches
21 conflicts
0xc964c25d…a434
0x40c49f…2af0
13 touches
21 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x2b54cadb…4425
0xd18b7e…414b
10 touches
10 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0x4d42f16e…a6c9
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
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: Kuru Exchange: MarginAccount
21 conflicts on slot 0x6518075e89…5f2b17
Audit this contract →
← previous block·next block →recent activity