← previous blocknext block →recent activity
Analyzing
Block #98,420,590
40 transactions · 39 stateful · 2026-08-23 07:35:02 UTC
Parallelism
88/100
Blocked
18%
Avg conflicts / tx
0.23
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,420,590 · 40 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
1w02w13w26w37w08w113w238w439w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x304881de…eedd
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x403a4649…d8be
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7c51d9aa…af39
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x443a3e47…f4a4
0x065c9d…c394
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