← previous blocknext block →recent activity

Analyzing

Block #102,744,349

30 transactions · 28 stateful · 2026-09-07 11:39:57 UTC

Parallelism

67/100

Blocked

50%

Avg conflicts / tx

1.83

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #102,744,349  ·  30 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xb87af72a…aef6

0x2a68ba…90c5

14 touches
21 conflicts

0x75f3ef89…16a5

0x065c9d…c394

13 touches
21 conflicts

0x002fed35…79fa

0x2a68ba…90c5

12 touches
15 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0xa605468c…1bfc

0x34ae4d…3fc5

8 touches
6 conflicts

0x48ed1159…abe9

0x34ae4d…3fc5

8 touches
6 conflicts

0x06e40499…165e

0x34ae4d…3fc5

8 touches
6 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