← previous blocknext block →recent activity
Analyzing
Block #100,859,184
28 transactions · 25 stateful · 2026-08-31 21:07:53 UTC
Parallelism
68/100
Blocked
60%
Avg conflicts / tx
1.18
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #100,859,184 · 28 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
1w02w13w24w35w47w09w010w111w012w114w117w518w619w720w221w123w827w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
10 touches
10 conflicts
0x46725ce2…be08
0xd32edf…ff58
9 touches
10 conflicts
0x2b54cadb…4425
0xd18b7e…414b
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x669276b5…eaef
0x40c49f…2af0
8 touches
6 conflicts
0xd996735f…8732
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 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
10 conflicts on slot 0x002fed350f…7379fa
Audit this contract →
← previous block·next block →recent activity