← previous blocknext block →recent activity
Analyzing
Block #98,930,464
21 transactions · 20 stateful · 2026-08-25 02:56:47 UTC
Parallelism
86/100
Blocked
40%
Avg conflicts / tx
0.48
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,930,464 · 21 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
4w05w06w17w08w19w010w112w113w115w117w018w220w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0002
0xbb3f3c…e046
4 touches
1 conflict
0xdcebb2b8…5f18
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x5092059d…81ff
0x851145…3f07
4 touches
1 conflict
0x77253a66…396f
0x851145…3f07
4 touches
1 conflict
0xebbe8dde…9ac7
0x851145…3f07
4 touches
1 conflict
0x2a354a63…0515
0x065c9d…c394
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity