← previous blocknext block →recent activity

Analyzing

Block #99,473,390

18 transactions · 17 stateful · 2026-08-27 00:35:43 UTC

Parallelism

83/100

Blocked

35%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #99,473,390  ·  18 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x065c9d…c394

6 touches
3 conflicts

0xfe2bac2b…2cec

0x065c9d…c394

6 touches
3 conflicts

0xd66696e0…0842

0x34b655…2a6f

4 touches
1 conflict

0x70d81211…f49f

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x8b780b26…f5ff

0x34b655…2a6f

4 touches
1 conflict

0x8e31e8e8…a6aa

0x34b655…2a6f

4 touches
1 conflict

0x9cf9008a…d826

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-MON/USDC

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity