Block #73,706,333

← previous blocknext block →recent activity

Analyzing

Block #73,706,333

25 transactions · 21 stateful · 2026-05-10 16:11:11 UTC

Parallelism

92/100

Blocked

19%

Avg conflicts / tx

0.16

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,706,333  ·  25 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

0x1b5d2e60…99b5

0x34b655…2a6f

4 touches
1 conflict

0x414e9446…4b59

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x6c53501e…7069

0x34b655…2a6f

4 touches
1 conflict

0x8aa1941d…2988

0x34b655…2a6f

4 touches
1 conflict

0xa8bd52b5…862e

0x34b655…2a6f

4 touches
1 conflict

0xa92c8763…6d7f

0x34b655…2a6f

4 touches
1 conflict

0xaa8a1c54…ead3

0x34b655…2a6f

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

1 conflict on slot 0x1b5d2e607a…9999b5

← previous block·next block →recent activity