← previous blocknext block →recent activity

Analyzing

Block #73,651,274

21 transactions · 14 stateful · 2026-05-10 09:59:44 UTC

Parallelism

76/100

Blocked

43%

Avg conflicts / tx

0.62

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,651,274  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x3f407154…e0b9

0xd32edf…ff58

9 touches
10 conflicts

0x8973f578…6672

0x34b655…2a6f

6 touches
3 conflicts

0x38524fae…9deb

0x34b655…2a6f

6 touches
3 conflicts

0xb91a6f59…722c

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x64461c10…e86d

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…001b

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: 0xd32edf66…9fff58

10 conflicts on slot 0x3f4071541a…9de0b9

← previous block·next block →recent activity