Block #73,210,734

← previous blocknext block →recent activity

Analyzing

Block #73,210,734

12 transactions · 12 stateful · 2026-05-08 09:06:46 UTC

Parallelism

58/100

Blocked

42%

Avg conflicts / tx

1

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,210,734  ·  12 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

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x7f189cf6…afab

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xe1133d90…18eb

0x065c9d…c394

4 touches
1 conflict

0x9c5bb81d…bffe

0x065c9d…c394

4 touches
1 conflict

0xd7bc44cb…5c46

0x065c9d…c394

3 touches
1 conflict

0xdcf28f30…49c2

0x065c9d…c394

3 touches
1 conflict

0x977f2845…7241

0x065c9d…c394

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

6 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity