← previous blocknext block →recent activity
Analyzing
Block #98,566,951
31 transactions · 27 stateful · 2026-08-23 20:04:33 UTC
Parallelism
84/100
Blocked
33%
Avg conflicts / tx
0.39
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,566,951 · 31 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w18w313w014w115w021w422w126w229w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffe431af…8faa
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
6 touches
3 conflicts
0x0b8007b4…4fda
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001e
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: Market-MON/USDC
3 conflicts on slot 0xffe431af56…838faa
Audit this contract →
← previous block·next block →recent activity