← previous blocknext block →recent activity

Analyzing

Block #98,015,120

20 transactions · 20 stateful · 2026-08-21 21:34:08 UTC

Parallelism

85/100

Blocked

30%

Avg conflicts / tx

0.35

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #98,015,120  ·  20 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xb31eb7d3…64eb

0xa6afd3…d132

6 touches
3 conflicts

0xd6bd849a…5597

0x2a68ba…90c5

4 touches
1 conflict

0x10abefc9…c9bc

0x2b46c0…1669

4 touches
1 conflict

0x10d80fee…dbda

0x2b46c0…1669

4 touches
1 conflict

0x2f4b2cf9…4e1e

0x2b46c0…1669

4 touches
1 conflict

0x40970e69…da50

0x2b46c0…1669

4 touches
1 conflict

0x595839b9…ca61

0x2b46c0…1669

4 touches
1 conflict

0x7aa91b8f…d070

0x2b46c0…1669

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-WETH/USDC

3 conflicts on slot 0xb31eb7d3a6…6e64eb

← previous block·next block →recent activity