← previous blocknext block →recent activity

Analyzing

Block #73,651,434

15 transactions · 14 stateful · 2026-05-10 10:00:48 UTC

Parallelism

80/100

Blocked

43%

Avg conflicts / tx

0.53

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,651,434  ·  15 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

0x38524fae…9deb

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x96b01960…163d

0x34b655…2a6f

4 touches
1 conflict

0x3a9550c7…abb9

0xd32edf…ff58

3 touches
1 conflict

0x00000000…002b

0x1b6862…e19c

2 touches
0 conflicts

0xba5743c7…21c2

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: 0x34b6552d…112a6f

3 conflicts on slot 0x38524faed4…ae9deb

← previous block·next block →recent activity