← previous blocknext block →recent activity

Analyzing

Block #73,437,985

13 transactions · 12 stateful · 2026-05-09 10:18:39 UTC

Parallelism

54/100

Blocked

50%

Avg conflicts / tx

1.54

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,437,985  ·  13 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

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x69017fce…85c2

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0xd11260e7…3609

0x065c9d…c394

4 touches
1 conflict

0x51e1366d…7f1d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

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

15 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity