← previous blocknext block →recent activity
Analyzing
Block #100,851,258
12 transactions · 12 stateful · 2026-08-31 20:28:01 UTC
Parallelism
67/100
Blocked
58%
Avg conflicts / tx
1.08
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,851,258 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w08w19w210w311w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x486628ad…cecd
0x40c49f…2af0
8 touches
6 conflicts
0x2b54cadb…4425
0xd18b7e…414b
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x83fc4fc1…6fe1
0x34ae4d…3fc5
2 touches
0 conflicts
0xa605468c…1bfc
0x34ae4d…3fc5
2 touches
0 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
6 conflicts on slot 0x002fed350f…7379fa
Audit this contract →
← previous block·next block →recent activity