← previous blocknext block →recent activity

Analyzing

Block #93,181,323

14 transactions · 13 stateful · 2026-08-04 22:35:24 UTC

Parallelism

86/100

Blocked

23%

Avg conflicts / tx

0.21

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #93,181,323  ·  14 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

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x0be747d5…22e0

0x34b655…2a6f

4 touches
1 conflict

0x0be747d5…22e1

0x34b655…2a6f

4 touches
1 conflict

0x1d351a9b…f2dd

0x34b655…2a6f

4 touches
1 conflict

0x3fd6704a…63a9

0x34b655…2a6f

4 touches
1 conflict

0x4ae1e116…4249

0x34b655…2a6f

4 touches
1 conflict

0x53fdd349…c3f2

0x34b655…2a6f

4 touches
1 conflict

0xf8010f18…5cb4

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 0x0000000000…00003d

← previous block·next block →recent activity