← previous blocknext block →recent activity

Analyzing

Block #85,180,186

20 transactions · 17 stateful · 2026-07-02 20:02:30 UTC

Parallelism

70/100

Blocked

47%

Avg conflicts / tx

0.6

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #85,180,186  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x3e1c3586…83d7

0xa6afd3…d132

6 touches
3 conflicts

0x987aeb55…0e2a

0xa6afd3…d132

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x78067279…d187

0x34b655…2a6f

4 touches
1 conflict

0xa678cd56…4fab

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity