← previous blocknext block →recent activity

Analyzing

Block #85,898,323

18 transactions · 14 stateful · 2026-07-06 03:46:11 UTC

Parallelism

89/100

Blocked

21%

Avg conflicts / tx

0.28

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #85,898,323  ·  18 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

0x7bdb6a0a…091e

0xa6afd3…d132

4 touches
1 conflict

0x05b1b07a…7a99

0x34b655…2a6f

4 touches
1 conflict

0x10326aa1…38a3

0x34b655…2a6f

4 touches
1 conflict

0x1aaf4996…65ec

0x34b655…2a6f

4 touches
1 conflict

0x1e093e63…e4ef

0x34b655…2a6f

4 touches
1 conflict

0x23253ea8…e0a4

0x34b655…2a6f

4 touches
1 conflict

0x79548f93…0619

0x34b655…2a6f

4 touches
1 conflict

0x7e17e82a…9748

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 0x7bdb6a0acc…20091e

← previous block·next block →recent activity