← previous blocknext block →recent activity
Analyzing
Block #100,852,947
23 transactions · 21 stateful · 2026-08-31 20:36:31 UTC
Parallelism
74/100
Blocked
52%
Avg conflicts / tx
1.39
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,852,947 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w37w412w413w514w115w216w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6518075e…2b17
0x2a68ba…90c5
12 touches
15 conflicts
0x2b54cadb…4425
0xd18b7e…414b
12 touches
15 conflicts
0x084aba0c…43c7
0x40c49f…2af0
12 touches
15 conflicts
0xf3ee5d32…cf0d
0xd32edf…ff58
11 touches
15 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x00000000…002b
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 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