← previous blocknext block →recent activity

Analyzing

Block #102,872,032

33 transactions · 27 stateful · 2026-09-07 22:25:35 UTC

Parallelism

79/100

Blocked

48%

Avg conflicts / tx

1.06

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #102,872,032  ·  33 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

14 touches
21 conflicts

0xfcb7b8b2…ebb3

0x065c9d…c394

12 touches
15 conflicts

0xb686e6f5…f6d1

0xc8689a…ee79

8 touches
6 conflicts

0xaad6be10…0801

0x2a68ba…90c5

8 touches
6 conflicts

0x06e40499…165e

0x34ae4d…3fc5

8 touches
6 conflicts

0xa605468c…1bfc

0x34ae4d…3fc5

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x49f5965e…7d53

0x34b655…2a6f

6 touches
3 conflicts

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

21 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity