← previous blocknext block →recent activity

Analyzing

Block #73,048,367

16 transactions · 15 stateful · 2026-05-07 15:06:30 UTC

Parallelism

63/100

Blocked

47%

Avg conflicts / tx

1.13

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,048,367  ·  16 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

0x6fe8bc4a…a01c

0xd32edf…ff58

11 touches
15 conflicts

0x6c6f37ba…c20c

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001f

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002f

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

15 conflicts on slot 0x6fe8bc4a41…1ca01c

← previous block·next block →recent activity