← previous blocknext block →recent activity
Analyzing
Block #98,662,328
19 transactions · 18 stateful · 2026-08-24 04:21:22 UTC
Parallelism
63/100
Blocked
33%
Avg conflicts / tx
1.16
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #98,662,328 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w07w18w29w310w411w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
14 touches
21 conflicts
0x9b759d10…9eb3
0xa6afd3…d132
13 touches
21 conflicts
0x11b69a7e…334e
0xee8c0e…1242
12 touches
15 conflicts
0xa1087a5c…66c4
0x754704…b603
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0018
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0028
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: MarginAccount
21 conflicts on slot 0x002fed350f…7379fa
Audit this contract →
← previous block·next block →recent activity