← previous blocknext block →recent activity

Analyzing

Block #98,274,964

9 transactions · 9 stateful · 2026-08-22 19:22:21 UTC

Parallelism

78/100

Blocked

33%

Avg conflicts / tx

0.33

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #98,274,964  ·  9 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xc45e4fb5…7cc3

0xa6afd3…d132

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x731d7308…fd26

0x34b655…2a6f

4 touches
1 conflict

0x898d9b8a…d1ef

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x15c6ded9…48e7

0x754704…b603

4 touches
1 conflict

0x5a7e4e98…1f3b

0x754704…b603

4 touches
1 conflict

0xd4c946a4…b8d4

0x754704…b603

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

1 conflict on slot 0xc45e4fb512…447cc3

← previous block·next block →recent activity