Block #73,200,619

← previous blocknext block →recent activity

Analyzing

Block #73,200,619

15 transactions · 13 stateful · 2026-05-08 07:59:29 UTC

Parallelism

73/100

Blocked

38%

Avg conflicts / tx

0.4

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,200,619  ·  15 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

0x251861eb…78fd

0x34b655…2a6f

6 touches
3 conflicts

0x8a35acfb…d1ac

0x8d66a4…3095

4 touches
1 conflict

0xe89e1a22…ce49

0x8d66a4…3095

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0xc6417de0…2191

0xc8689a…ee79

4 touches
1 conflict

0x72a2c989…8daa

0x065c9d…c394

2 touches
0 conflicts

0x8e66da19…66b6

0x065c9d…c394

2 touches
0 conflicts

0x93cd481c…a02a

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: 0x34b6552d…112a6f

3 conflicts on slot 0x251861ebbf…b678fd

← previous block·next block →recent activity