← previous blocknext block →recent activity
Analyzing
Block #98,748,509
83 transactions · 80 stateful · 2026-08-24 11:41:02 UTC
Parallelism
95/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,748,509 · 83 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w08w110w011w116w017w118w076w178w179w281w282w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x171d9a84…b3b7
0x34b655…2a6f
4 touches
1 conflict
0x215a6da4…0e86
0x34b655…2a6f
4 touches
1 conflict
0x272dc9b8…1b58
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6bc18f1e…b4ad
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity