← previous blocknext block →recent activity
Analyzing
Block #100,851,818
23 transactions · 20 stateful · 2026-08-31 20:30:50 UTC
Parallelism
61/100
Blocked
70%
Avg conflicts / tx
1.43
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #100,851,818 · 23 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w09w110w211w312w413w314w415w516w617w721w822w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
14 touches
21 conflicts
0x7a27f469…35b8
0x40c49f…2af0
13 touches
21 conflicts
0xa1087a5c…66c4
0x754704…b603
12 touches
15 conflicts
0x2b54cadb…4425
0xd18b7e…414b
12 touches
15 conflicts
0x91ad21da…9ad1
0xd32edf…ff58
7 touches
6 conflicts
0x5c455afd…ce06
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
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
21 conflicts on slot 0x002fed350f…7379fa
Audit this contract →
← previous block·next block →recent activity