Block #73,693,568

← previous blocknext block →recent activity

Analyzing

Block #73,693,568

9 transactions · 7 stateful · 2026-05-10 14:45:05 UTC

Parallelism

78/100

Blocked

14%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,693,568  ·  9 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

0xa92c8763…6d7f

0x34b655…2a6f

4 touches
1 conflict

0x1f876d5b…dee3

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xe3693869…566b

0x34b655…2a6f

4 touches
1 conflict

0x3e733ae4…4598

0x34b655…2a6f

4 touches
1 conflict

0x97b0b2ee…4666

0x34b655…2a6f

4 touches
1 conflict

0x1f07a4dc…5754

0x3bd359…433a

2 touches
0 conflicts

0x143dba04…1b98

0x8d66a4…3095

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

1 conflict on slot 0xa92c87634b…146d7f

← previous block·next block →recent activity