← previous blocknext block →recent activity

Analyzing

Block #100,734,288

17 transactions · 16 stateful · 2026-08-31 10:39:12 UTC

Parallelism

88/100

Blocked

19%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #100,734,288  ·  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

0xb26ff3de…9352

0xa6afd3…d132

4 touches
1 conflict

0x261cbea7…e35d

0x34b655…2a6f

4 touches
1 conflict

0x261cbea7…e35e

0x34b655…2a6f

4 touches
1 conflict

0x33944a91…32df

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x89ac61bf…9443

0x34b655…2a6f

4 touches
1 conflict

0x963981cd…90c0

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

1 conflict on slot 0xb26ff3ded7…a89352

← previous block·next block →recent activity