← previous blocknext block →recent activity

Analyzing

Block #88,343,107

17 transactions · 16 stateful · 2026-07-17 12:11:22 UTC

Parallelism

88/100

Blocked

19%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #88,343,107  ·  17 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

0x1d86f412…d0b5

0xa6afd3…d132

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xad851f08…9005

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xbf47a88f…7b7e

0x34b655…2a6f

4 touches
1 conflict

0xbf47a88f…7b7f

0x34b655…2a6f

4 touches
1 conflict

0xdaee5e38…4986

0x34b655…2a6f

4 touches
1 conflict

0xebc9f918…9f11

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 0x1d86f412d3…55d0b5

← previous block·next block →recent activity