← previous blocknext block →recent activity
Analyzing
Block #98,418,399
10 transactions · 10 stateful · 2026-08-23 07:24:00 UTC
Parallelism
70/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,418,399 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcb7b8b2…ebb3
0x065c9d…c394
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xcca8f97b…d8db
0x065c9d…c394
3 touches
1 conflict
0xcd8fba61…f35f
0x065c9d…c394
3 touches
1 conflict
0x00000000…0006
0x010592…1c83
2 touches
0 conflicts
0x7f16a781…7962
0x065c9d…c394
2 touches
0 conflicts
0x28e527c8…c6f2
0x3bd359…433a
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-MON/USDC
1 conflict on slot 0xfcb7b8b239…6bebb3
Audit this contract →
← previous block·next block →recent activity