← previous blocknext block →recent activity
Analyzing
Block #100,856,260
30 transactions · 29 stateful · 2026-08-31 20:53:11 UTC
Parallelism
77/100
Blocked
48%
Avg conflicts / tx
1.3
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,856,260 · 30 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w09w010w111w514w015w116w217w319w420w523w129w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6518075e…2b17
0x2a68ba…90c5
12 touches
15 conflicts
0x9036b423…40b8
0xd32edf…ff58
11 touches
15 conflicts
0x43780690…e1bb
0x40c49f…2af0
11 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001c
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002c
0x1b6862…e19c
10 touches
10 conflicts
0x2ce2d49e…d189
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
15 conflicts on slot 0x6518075e89…5f2b17
Audit this contract →
← previous block·next block →recent activity