← previous blocknext block →recent activity
Analyzing
Block #98,581,843
32 transactions · 29 stateful · 2026-08-23 21:22:05 UTC
Parallelism
84/100
Blocked
34%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,581,843 · 32 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
1w03w14w06w08w110w211w113w214w315w316w430w131w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xbbee74c2…567a
0x065c9d…c394
6 touches
3 conflicts
0x24968e6d…0132
0x065c9d…c394
6 touches
3 conflicts
0x0b10f1de…fc43
0x34b655…2a6f
4 touches
1 conflict
0x0b3eb43a…ca08
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xa9988419…9f45
0x34b655…2a6f
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