← previous blocknext block →recent activity

Analyzing

Block #73,695,993

8 transactions · 6 stateful · 2026-05-10 15:01:23 UTC

Parallelism

75/100

Blocked

17%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,695,993  ·  8 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001c

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb84

0x1b6862…e19c

4 touches
1 conflict

0xc38a9aab…dae1

0xd32edf…ff58

3 touches
1 conflict

0xa4e3b3b1…0911

0x2a68ba…90c5

2 touches
0 conflicts

0x00000000…0003

0x465a0b…3980

2 touches
0 conflicts

0x00000000…0004

0x465a0b…3980

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: 0x1b68626d…2de19c

1 conflict on slot 0xd9f18d9a4a…7f141d

← previous block·next block →recent activity