← previous blocknext block →recent activity

Analyzing

Block #73,501,672

18 transactions · 18 stateful · 2026-05-09 17:22:32 UTC

Parallelism

78/100

Blocked

39%

Avg conflicts / tx

0.67

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,501,672  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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…0001

0x3704e4…e36f

8 touches
6 conflicts

0x00000000…0000

0x3704e4…e36f

8 touches
6 conflicts

0x44ad89ba…cf83

0xb68427…7777

8 touches
6 conflicts

0xea8e8e68…ba34

0x3bd359…433a

8 touches
6 conflicts

0xa472d565…9fe4

0x3bd359…433a

8 touches
6 conflicts

0x8b144217…a58e

0xb68427…7777

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

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: 0x3704e421…3ae36f

6 conflicts on slot 0x0000000000…000001

← previous block·next block →recent activity