← previous blocknext block →recent activity
Analyzing
Block #98,649,513
33 transactions · 28 stateful · 2026-08-24 03:14:21 UTC
Parallelism
88/100
Blocked
46%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,649,513 · 33 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w18w212w013w114w217w018w119w021w023w225w126w127w329w030w131w232w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0x70ef7b6e…fdb6
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c6
0x1b6862…e19c
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
6 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity