← previous blocknext block →recent activity

Analyzing

Block #73,503,052

13 transactions · 11 stateful · 2026-05-09 17:31:45 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,503,052  ·  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

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0x22e295f5…1bef

0x065c9d…c394

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xa27fa22d…7dca

0x54cd53…9e7d

2 touches
0 conflicts

0x02952e27…66f1

0x6657d1…8ccc

2 touches
0 conflicts

0x04c9144d…356b

0x6657d1…8ccc

2 touches
0 conflicts

0x0a375507…6b32

0x6657d1…8ccc

2 touches
0 conflicts

0x0b03a3c2…63c1

0x6657d1…8ccc

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: 0x2a68ba18…8e90c5

15 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity