← previous blocknext block →recent activity

Analyzing

Block #94,467,140

23 transactions · 16 stateful · 2026-08-09 10:37:16 UTC

Parallelism

78/100

Blocked

44%

Avg conflicts / tx

0.43

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #94,467,140  ·  23 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x21898044…a071

0x065c9d…c394

6 touches
3 conflicts

0x80afd9d9…57cf

0x065c9d…c394

6 touches
3 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0000

0x63e48b…53f2

6 touches
3 conflicts

0x00000000…0002

0x63e48b…53f2

6 touches
3 conflicts

0x00000000…0004

0x63e48b…53f2

6 touches
3 conflicts

0x9a555477…19a8

0x754704…b603

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity