← previous blocknext block →recent activity

Analyzing

Block #98,480,098

13 transactions · 12 stateful · 2026-08-23 12:34:47 UTC

Parallelism

85/100

Blocked

17%

Avg conflicts / tx

0.23

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #98,480,098  ·  13 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

0x68106229…7057

0xa6afd3…d132

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0xa02838a3…bc54

0x34b655…2a6f

4 touches
1 conflict

0xbff3a360…6ae5

0x34b655…2a6f

4 touches
1 conflict

0xc7f6eab9…9e9f

0x34b655…2a6f

4 touches
1 conflict

0xe26c4e53…94c2

0x34b655…2a6f

4 touches
1 conflict

0xe26c4e53…94c3

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

1 conflict on slot 0x68106229be…ec7057

← previous block·next block →recent activity