← previous blocknext block →recent activity
Analyzing
Block #102,567,311
26 transactions · 26 stateful · 2026-09-06 20:47:08 UTC
Parallelism
54/100
Blocked
54%
Avg conflicts / tx
2.35
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #102,567,311 · 26 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w69w713w816w917w1019w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaad6be10…0801
0x2a68ba…90c5
18 touches
36 conflicts
0x858723e0…edaa
0xd32edf…ff58
17 touches
36 conflicts
0xd0ec60a1…d246
0x1b6862…e19c
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…001e
0x1b6862…e19c
16 touches
28 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 0xaad6be10ae…2c0801
Audit this contract →
← previous block·next block →recent activity