← previous blocknext block →recent activity

Analyzing

Block #93,681,568

19 transactions · 17 stateful · 2026-08-06 16:30:20 UTC

Parallelism

89/100

Blocked

29%

Avg conflicts / tx

0.32

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #93,681,568  ·  19 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

0x439cfb2c…7b9e

0xa6afd3…d132

4 touches
1 conflict

0x1bf8d2af…d140

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xc6b9bb4b…145a

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd676e291…3ecf

0x34b655…2a6f

4 touches
1 conflict

0xd9d7dc71…b222

0x34b655…2a6f

4 touches
1 conflict

0xa1087a5c…66c4

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 0x439cfb2c22…b27b9e

← previous block·next block →recent activity