Block #73,348,614

← previous blocknext block →recent activity

Analyzing

Block #73,348,614

21 transactions · 18 stateful · 2026-05-09 00:24:01 UTC

Parallelism

71/100

Blocked

28%

Avg conflicts / tx

0.9

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,348,614  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x4d87512b…897c

0x065c9d…c394

8 touches
6 conflicts

0x22e295f5…1bef

0x065c9d…c394

6 touches
3 conflicts

0x3f8a32f1…e6e9

0xd32edf…ff58

3 touches
1 conflict

0x398167bd…0689

0x065c9d…c394

3 touches
1 conflict

0xf90e5e87…3018

0x065c9d…c394

3 touches
1 conflict

0x0b000000…0002

0x000000…1000

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

15 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity