← previous blocknext block →recent activity
Analyzing
Block #98,914,442
35 transactions · 21 stateful · 2026-08-25 01:36:11 UTC
Parallelism
86/100
Blocked
33%
Avg conflicts / tx
0.37
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,914,442 · 35 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
1w012w013w114w215w016w025w127w128w129w330w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x2a354a63…0515
0x065c9d…c394
6 touches
3 conflicts
0x3ab98f65…0774
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xbb97db90…4c93
0xc8689a…ee79
4 touches
1 conflict
0x0778475b…bd75
0x2a68ba…90c5
4 touches
1 conflict
0xd984a5e4…5cfc
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity