← previous blocknext block →recent activity

Analyzing

Block #73,359,721

13 transactions · 12 stateful · 2026-05-09 01:37:49 UTC

Parallelism

85/100

Blocked

17%

Avg conflicts / tx

0.15

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,359,721  ·  13 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x408e66bb…3d6b

0x34b655…2a6f

4 touches
1 conflict

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…0004

0x5afd3e…7620

2 touches
0 conflicts

0x27842681…aa67

0x5afd3e…7620

2 touches
0 conflicts

0xeb790d87…495e

0x5afd3e…7620

2 touches
0 conflicts

0x3378e8b6…20a9

0x754704…b603

2 touches
0 conflicts

0x4039b31f…0f4a

0x754704…b603

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: 0x34b6552d…112a6f

1 conflict on slot 0x408e66bba7…d43d6b

← previous block·next block →recent activity