← previous blocknext block →recent activity

Analyzing

Block #73,434,332

10 transactions · 8 stateful · 2026-05-09 09:54:22 UTC

Parallelism

80/100

Blocked

13%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,434,332  ·  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

0xe5b23c08…02c2

0x34b655…2a6f

4 touches
1 conflict

0x4546ebad…b908

0x34b655…2a6f

4 touches
1 conflict

0xa15427f6…d932

0x34b655…2a6f

4 touches
1 conflict

0xac206e47…ef7d

0x34b655…2a6f

4 touches
1 conflict

0xb4f79daa…7a86

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x0eac6378…36f4

0x34b655…2a6f

2 touches
0 conflicts

0x5138188e…796b

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 0xe5b23c08c2…2902c2

← previous block·next block →recent activity