Block #73,469,114

← previous blocknext block →recent activity

Analyzing

Block #73,469,114

10 transactions · 10 stateful · 2026-05-09 13:45:53 UTC

Parallelism

80/100

Blocked

20%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,469,114  ·  10 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

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x6f08361d…bda6

0x065c9d…c394

4 touches
1 conflict

0x22e0cc1d…ad04

0x34b655…2a6f

4 touches
1 conflict

0x1a7e478a…37a5

0x34b655…2a6f

2 touches
0 conflicts

0x4df472f9…688e

0x34b655…2a6f

2 touches
0 conflicts

0x97b0b2ee…4666

0x34b655…2a6f

2 touches
0 conflicts

0xa15427f6…d932

0x34b655…2a6f

2 touches
0 conflicts

0xa92c8763…6d7f

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: 0x2a68ba18…8e90c5

1 conflict on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity