← previous blocknext block →recent activity
Analyzing
Block #102,816,867
22 transactions · 19 stateful · 2026-09-07 17:47:59 UTC
Parallelism
55/100
Blocked
47%
Avg conflicts / tx
1.5
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #102,816,867 · 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
1w02w13w24w310w411w512w613w714w820w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
16 touches
28 conflicts
0x20ce95a4…6118
0x40c49f…2af0
15 touches
28 conflicts
0x2b54cadb…4425
0xd18b7e…414b
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x06ce5d4b…c122
0x34ae4d…3fc5
4 touches
1 conflict
0x3e1e8e54…9c83
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
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
28 conflicts on slot 0x002fed350f…7379fa
Audit this contract →
← previous block·next block →recent activity