Block #73,698,265

← previous blocknext block →recent activity

Analyzing

Block #73,698,265

7 transactions · 7 stateful · 2026-05-10 15:16:45 UTC

Parallelism

71/100

Blocked

14%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,698,265  ·  7 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

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

0x54af419a…ad0d

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x0ac31945…2c72

0x065c9d…c394

2 touches
0 conflicts

0x371682fd…8073

0x065c9d…c394

2 touches
0 conflicts

0x4a15ff0f…4abf

0x065c9d…c394

2 touches
0 conflicts

0x4e6a2757…6fd4

0x065c9d…c394

2 touches
0 conflicts

0x529acb6a…fcc6

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

1 conflict on slot 0xc9e9752290…9c3519

← previous block·next block →recent activity