← previous blocknext block →recent activity
Analyzing
Block #98,061,426
15 transactions · 14 stateful · 2026-08-22 01:27:17 UTC
Parallelism
87/100
Blocked
36%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,061,426 · 15 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w06w07w19w110w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf88ccd07…a684
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x280a5900…fe6f
0x34b655…2a6f
4 touches
1 conflict
0xb3aa2022…9e09
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002c
0x1b6862…e19c
2 touches
0 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-WETH/USDC
1 conflict on slot 0xf88ccd07d5…f2a684
Audit this contract →
← previous block·next block →recent activity