← previous blocknext block →recent activity

Analyzing

Block #93,182,625

19 transactions · 19 stateful · 2026-08-04 22:41:57 UTC

Parallelism

89/100

Blocked

26%

Avg conflicts / tx

0.37

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #93,182,625  ·  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

0xb88bd44f…0a6e

0xa6afd3…d132

4 touches
1 conflict

0x1803586e…d149

0xa6afd3…d132

4 touches
1 conflict

0x3464bbc5…a323

0xa6afd3…d132

4 touches
1 conflict

0x4acbdbcf…a8c6

0x34b655…2a6f

4 touches
1 conflict

0x4e8c4408…d37a

0x34b655…2a6f

4 touches
1 conflict

0x4e8c4408…d37b

0x34b655…2a6f

4 touches
1 conflict

0x4f5af78f…9b97

0x34b655…2a6f

4 touches
1 conflict

0x54a7b790…c2c6

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 0xb88bd44f74…f00a6e

← previous block·next block →recent activity