← previous blocknext block →recent activity

Analyzing

Block #73,651,235

20 transactions · 17 stateful · 2026-05-10 09:59:29 UTC

Parallelism

60/100

Blocked

47%

Avg conflicts / tx

1.4

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,651,235  ·  20 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x987e5cb2…c6d0

0xd32edf…ff58

13 touches
21 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

10 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0xd5a25205…645a

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001b

0x1b6862…e19c

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: 0xd32edf66…9fff58

21 conflicts on slot 0x987e5cb215…6dc6d0

← previous block·next block →recent activity