← previous blocknext block →recent activity
Analyzing
Block #98,502,410
58 transactions · 51 stateful · 2026-08-23 14:27:43 UTC
Parallelism
84/100
Blocked
63%
Avg conflicts / tx
1.59
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #98,502,410 · 58 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w08w09w111w212w313w414w515w619w120w221w322w423w530w134w237w338w444w549w653w754w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
14 touches
21 conflicts
0xbb840b8c…33cb
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0002
0xbb3f3c…e046
12 touches
15 conflicts
0xa605468c…1bfc
0x2b46c0…1669
10 touches
10 conflicts
0xbb97db90…4c93
0xc8689a…ee79
10 touches
10 conflicts
0xbad68552…e6bf
0x34b655…2a6f
10 touches
10 conflicts
0x24968e6d…0132
0x065c9d…c394
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 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: Market-MON/USDC
21 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity