← previous blocknext block →recent activity

Analyzing

Block #73,214,557

21 transactions · 19 stateful · 2026-05-08 09:32:07 UTC

Parallelism

71/100

Blocked

37%

Avg conflicts / tx

0.9

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,214,557  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xa6333302…89e4

0xd32edf…ff58

11 touches
15 conflicts

0xcb45d9d6…cb83

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001b

0x1b6862…e19c

6 touches
3 conflicts

0x47c1a8e8…f74a

0x34b655…2a6f

4 touches
1 conflict

0xcd5c3e98…2daf

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xfe3d37ee…6e67

0x34b655…2a6f

4 touches
1 conflict

0x0335ae80…8414

0x8d66a4…3095

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

15 conflicts on slot 0xa6333302d9…8989e4

← previous block·next block →recent activity