← previous blocknext block →recent activity

Analyzing

Block #73,490,489

17 transactions · 11 stateful · 2026-05-09 16:08:08 UTC

Parallelism

65/100

Blocked

45%

Avg conflicts / tx

0.88

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,490,489  ·  17 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

0x37f26310…06f8

0xd32edf…ff58

11 touches
15 conflicts

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x18aed20c…48f3

0x000000…012a

2 touches
0 conflicts

0x2fb6ddd2…b2a4

0x000000…012a

2 touches
0 conflicts

0x335a161d…fe7f

0x000000…012a

2 touches
0 conflicts

0x2c98155e…205c

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

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

15 conflicts on slot 0x37f263104e…1606f8

← previous block·next block →recent activity