← previous blocknext block →recent activity
Analyzing
Block #98,079,859
34 transactions · 22 stateful · 2026-08-22 03:00:03 UTC
Parallelism
88/100
Blocked
45%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,079,859 · 34 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
1w07w010w011w113w221w122w323w224w025w126w228w029w130w031w133w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x41755291…977f
0x065c9d…c394
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x49299fcf…c552
0x34b655…2a6f
6 touches
3 conflicts
0xf79df061…e005
0xe52b14…7230
6 touches
3 conflicts
0x45f562b2…9294
0x2b46c0…1669
4 touches
1 conflict
0x8488f10f…9353
0x2b46c0…1669
4 touches
1 conflict
0x8488f10f…9354
0x2b46c0…1669
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity