Block #73,343,607

← previous blocknext block →recent activity

Analyzing

Block #73,343,607

19 transactions · 16 stateful · 2026-05-08 23:50:42 UTC

Parallelism

79/100

Blocked

31%

Avg conflicts / tx

0.53

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,343,607  ·  19 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0xa15427f6…d932

0x34b655…2a6f

6 touches
3 conflicts

0xb4f79daa…7a86

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xe5b23c08…02c2

0x34b655…2a6f

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xc5b5128a…c5b2

0x065c9d…c394

4 touches
1 conflict

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity