← previous blocknext block →recent activity

Analyzing

Block #73,359,635

14 transactions · 12 stateful · 2026-05-09 01:37:14 UTC

Parallelism

71/100

Blocked

42%

Avg conflicts / tx

0.64

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,359,635  ·  14 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…0002

0xab3526…fa38

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0x3a787979…8acc

0x065c9d…c394

2 touches
0 conflicts

0x6fed7cdd…d079

0x065c9d…c394

2 touches
0 conflicts

0xb08e998f…97b7

0x065c9d…c394

2 touches
0 conflicts

0xcbaf5368…c5d4

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: 0xab35264b…1cfa38

6 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity