← previous blocknext block →recent activity
Analyzing
Block #98,432,671
23 transactions · 20 stateful · 2026-08-23 08:35:49 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,432,671 · 23 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
1w02w03w05w17w19w010w111w012w113w214w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xbb97db90…4c93
0xc8689a…ee79
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0002
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0004
0x63e48b…53f2
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x9a555477…19a8
0x754704…b603
4 touches
1 conflict
0x00000000…0002
0xbb3f3c…e046
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