← previous blocknext block →recent activity

Analyzing

Block #73,201,442

13 transactions · 11 stateful · 2026-05-08 08:04:58 UTC

Parallelism

54/100

Blocked

45%

Avg conflicts / tx

1.15

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,201,442  ·  13 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

0x7f189cf6…afab

0x065c9d…c394

12 touches
15 conflicts

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x92339d95…0800

0x0000a8…8888

2 touches
0 conflicts

0x02263f69…ed74

0x065c9d…c394

2 touches
0 conflicts

0x8c64d0b4…242c

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0004

0x35fa64…a655

2 touches
0 conflicts

0x00000000…0002

0xab3526…fa38

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: 0x065c9d28…a9c394

15 conflicts on slot 0x7f189cf621…beafab

← previous block·next block →recent activity