← previous blocknext block →recent activity

Analyzing

Block #73,647,601

19 transactions · 14 stateful · 2026-05-10 09:35:01 UTC

Parallelism

74/100

Blocked

57%

Avg conflicts / tx

0.79

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,647,601  ·  19 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

0x66196638…67b0

0xd32edf…ff58

7 touches
6 conflicts

0x22e295f5…1bef

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x7c991450…44a7

0x34b655…2a6f

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xae69c125…2379

0x2a68ba…90c5

4 touches
1 conflict

0x157b6348…8604

0x34b655…2a6f

4 touches
1 conflict

0x59ef13ba…2741

0x34b655…2a6f

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

6 conflicts on slot 0x66196638c6…1f67b0

← previous block·next block →recent activity