← previous blocknext block →recent activity

Analyzing

Block #73,446,620

16 transactions · 9 stateful · 2026-05-09 11:16:09 UTC

Parallelism

81/100

Blocked

22%

Avg conflicts / tx

0.19

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,446,620  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x4d8db150…f1a8

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…001f

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002f

0x1b6862…e19c

4 touches
1 conflict

0x5a3732cb…edb3

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

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

3 conflicts on slot 0x4d8db15081…52f1a8

← previous block·next block →recent activity