Block #73,705,374

← previous blocknext block →recent activity

Analyzing

Block #73,705,374

13 transactions · 11 stateful · 2026-05-10 16:04:42 UTC

Parallelism

85/100

Blocked

18%

Avg conflicts / tx

0.15

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,705,374  ·  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

0x9098f0db…b830

0x065c9d…c394

4 touches
1 conflict

0xb49a4dbe…f753

0x065c9d…c394

4 touches
1 conflict

0xf7001ecf…209d

0x065c9d…c394

3 touches
1 conflict

0x53694603…d2bc

0x065c9d…c394

3 touches
1 conflict

0x26bd67f7…e446

0x065c9d…c394

2 touches
0 conflicts

0x42a76424…234b

0x065c9d…c394

2 touches
0 conflicts

0x53cf5384…7f73

0x065c9d…c394

2 touches
0 conflicts

0xae69c125…2379

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

1 conflict on slot 0x9098f0db1a…0cb830

← previous block·next block →recent activity