← previous blocknext block →recent activity

Analyzing

Block #70,909,209

17 transactions · 17 stateful · 2026-04-27 17:28:14 UTC

Parallelism

82/100

Blocked

35%

Avg conflicts / tx

0.35

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #70,909,209  ·  17 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

0xbbee74c2…567a

0x131a2e…0da9

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x4ab14837…e1b2

0x2a68ba…90c5

4 touches
1 conflict

0x4039b31f…0f4a

0x754704…b603

4 touches
1 conflict

0xb9d2cf20…a668

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0004

0x5afd3e…7620

4 touches
1 conflict

0x1b228879…b5aa

0x5afd3e…7620

4 touches
1 conflict

0x48bbd314…2a9f

0x5afd3e…7620

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/AUSD

1 conflict on slot 0xbbee74c2e7…6e567a

← previous block·next block →recent activity