← previous blocknext block →recent activity
Analyzing
Block #98,663,664
40 transactions · 39 stateful · 2026-08-24 04:28:20 UTC
Parallelism
85/100
Blocked
54%
Avg conflicts / tx
1.1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #98,663,664 · 40 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
1w02w13w27w08w19w010w011w212w013w014w115w317w119w020w122w223w324w426w227w528w129w238w439w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
10 touches
10 conflicts
0x11b69a7e…334e
0xee8c0e…1242
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x4016a710…d256
0xa6afd3…d132
9 touches
10 conflicts
0x8c49c85c…ee96
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0028
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
10 conflicts on slot 0x002fed350f…7379fa
Audit this contract →
← previous block·next block →recent activity