Block #73,343,610

← previous blocknext block →recent activity

Analyzing

Block #73,343,610

15 transactions · 12 stateful · 2026-05-08 23:50:43 UTC

Parallelism

67/100

Blocked

33%

Avg conflicts / tx

0.4

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,343,610  ·  15 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xf537eaa0…73c8

0x065c9d…c394

6 touches
3 conflicts

0x6d09a421…50b7

0x065c9d…c394

3 touches
1 conflict

0x4b32b15f…4676

0xd32edf…ff58

3 touches
1 conflict

0x1a8c8b72…bc43

0x065c9d…c394

2 touches
0 conflicts

0x5ab3f9e0…131f

0x065c9d…c394

2 touches
0 conflicts

0x7b4b97ce…d915

0x065c9d…c394

2 touches
0 conflicts

0x8ccc8ff2…3ffe

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

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity