Block #73,492,483

← previous blocknext block →recent activity

Analyzing

Block #73,492,483

7 transactions · 6 stateful · 2026-05-09 16:21:24 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,492,483  ·  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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0x2f6503c3…b11b

0x065c9d…c394

2 touches
0 conflicts

0x48804c16…091e

0x065c9d…c394

2 touches
0 conflicts

0xa8b7f0b7…d7ac

0x065c9d…c394

2 touches
0 conflicts

0xac7ff9bb…139d

0x065c9d…c394

2 touches
0 conflicts

0xda6c31ec…ab5b

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