Block #73,917,700

← previous blocknext block →recent activity

Analyzing

Block #73,917,700

6 transactions · 6 stateful · 2026-05-11 15:47:38 UTC

Parallelism

67/100

Blocked

17%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,917,700  ·  6 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x47185b3a…8f4f

0x065c9d…c394

3 touches
1 conflict

0x4086863c…622a

0x065c9d…c394

3 touches
1 conflict

0x0366123c…9ee7

0x065c9d…c394

2 touches
0 conflicts

0x0c38465d…a3d8

0x065c9d…c394

2 touches
0 conflicts

0x2c2ae2ac…1742

0x065c9d…c394

2 touches
0 conflicts

0x45599156…2c62

0x065c9d…c394

2 touches
0 conflicts

0x56b33f2a…3e6b

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity