← previous blocknext block →recent activity

Analyzing

Block #73,795,570

12 transactions · 11 stateful · 2026-05-11 02:13:24 UTC

Parallelism

50/100

Blocked

45%

Avg conflicts / tx

0.83

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,795,570  ·  12 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

0x0ac31945…2c72

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xbea0a825…18ac

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…001e

0x1b6862…e19c

4 touches
1 conflict

0x529acb6a…fcc6

0x065c9d…c394

4 touches
1 conflict

0xcb45d9d6…cb86

0x1b6862…e19c

4 touches
1 conflict

0x07e02c84…70fd

0x188d58…ea8e

2 touches
0 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

6 conflicts on slot 0x0ac3194537…8f2c72

← previous block·next block →recent activity