← previous blocknext block →recent activity

Analyzing

Block #73,263,261

7 transactions · 6 stateful · 2026-05-08 14:56:03 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,263,261  ·  7 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

0xfa2527aa…9dd5

0x34b655…2a6f

4 touches
1 conflict

0x2c7e5699…a792

0x34b655…2a6f

4 touches
1 conflict

0xa92c8763…6d7f

0x34b655…2a6f

4 touches
1 conflict

0x47c1a8e8…f74a

0x34b655…2a6f

4 touches
1 conflict

0x693d979a…f2bd

0x34b655…2a6f

2 touches
0 conflicts

0xea02471d…1542

0x34b655…2a6f

2 touches
0 conflicts

0xf06c2cf5…61bd

0x34b655…2a6f

2 touches
0 conflicts

0xf6476f21…3580

0x34b655…2a6f

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 0xfa2527aaf5…479dd5

← previous block·next block →recent activity