← previous blocknext block →recent activity

Analyzing

Block #73,477,612

14 transactions · 13 stateful · 2026-05-09 14:42:21 UTC

Parallelism

64/100

Blocked

31%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,477,612  ·  14 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

0x4d1acd7c…f345

0x5e1b1a…7777

10 touches
10 conflicts

0x5593214e…dfc1

0x3bd359…433a

10 touches
10 conflicts

0x00000000…0000

0x75c3ab…4f0d

10 touches
10 conflicts

0x00000000…0001

0x75c3ab…4f0d

10 touches
10 conflicts

0x00000000…0003

0x75c3ab…4f0d

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

2 touches
0 conflicts

0x17a7f697…dcb1

0x1b6862…e19c

2 touches
0 conflicts

0xc9e97522…3519

0x2a68ba…90c5

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: 0x5e1b1a14…587777

10 conflicts on slot 0x4d1acd7cf0…b2f345

← previous block·next block →recent activity