← previous blocknext block →recent activity

Analyzing

Block #73,478,460

36 transactions · 25 stateful · 2026-05-09 14:48:00 UTC

Parallelism

86/100

Blocked

60%

Avg conflicts / tx

1.11

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,478,460  ·  36 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…0002

0xab3526…fa38

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xf308e6b2…fde1

0xd32edf…ff58

9 touches
10 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x00000000…0018

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0028

0x1b6862…e19c

6 touches
3 conflicts

0x3bd55803…5d48

0x1b6862…e19c

6 touches
3 conflicts

0x0f9b918b…212d

0x34b655…2a6f

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: 0xab35264b…1cfa38

10 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity