← previous blocknext block →recent activity
Analyzing
Block #100,851,565
18 transactions · 18 stateful · 2026-08-31 20:29:34 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
1.22
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,851,565 · 18 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
1w02w16w09w010w111w212w313w414w215w016w317w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6518075e…2b17
0x2a68ba…90c5
12 touches
15 conflicts
0x946f6c86…371d
0x40c49f…2af0
11 touches
15 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x2b54cadb…4425
0xd18b7e…414b
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x10797f0b…439a
0x34b655…2a6f
4 touches
1 conflict
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