← previous blocknext block →recent activity

Analyzing

Block #102,743,343

17 transactions · 15 stateful · 2026-09-07 11:34:53 UTC

Parallelism

65/100

Blocked

60%

Avg conflicts / tx

0.88

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #102,743,343  ·  17 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x659d53f9…7d2b

0x065c9d…c394

10 touches
10 conflicts

0x002fed35…79fa

0x2a68ba…90c5

10 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0xaad6be10…0801

0x2a68ba…90c5

4 touches
1 conflict

0x261cbea7…e35d

0x34b655…2a6f

4 touches
1 conflict

0x261cbea7…e35e

0x34b655…2a6f

4 touches
1 conflict

0x42c0a5d3…a476

0x34b655…2a6f

4 touches
1 conflict

0x46356904…5ead

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

10 conflicts on slot 0x659d53f9f7…767d2b

← previous block·next block →recent activity