← previous blocknext block →recent activity
Analyzing
Block #98,764,584
31 transactions · 25 stateful · 2026-08-24 13:02:02 UTC
Parallelism
87/100
Blocked
36%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,764,584 · 31 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
1w02w13w24w05w17w08w09w110w014w115w019w020w124w325w129w1
- 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
0x33018fbd…b0a1
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0002
0x0c428e…07a4
4 touches
1 conflict
0x00000000…0003
0x0c428e…07a4
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
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