← previous blocknext block →recent activity

Analyzing

Block #73,263,256

12 transactions · 10 stateful · 2026-05-08 14:56:01 UTC

Parallelism

75/100

Blocked

20%

Avg conflicts / tx

0.17

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,263,256  ·  12 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xbc04d98e…a484

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xfe3d37ee…6e67

0x34b655…2a6f

4 touches
1 conflict

0xdaca243a…f9de

0x34b655…2a6f

4 touches
1 conflict

0x79e405c3…815f

0x34b655…2a6f

4 touches
1 conflict

0x47c1a8e8…f74a

0x34b655…2a6f

4 touches
1 conflict

0xa92c8763…6d7f

0x34b655…2a6f

2 touches
0 conflicts

0xea02471d…1542

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 0xbc04d98e5a…d5a484

← previous block·next block →recent activity