Block #73,922,833

← previous blocknext block →recent activity

Analyzing

Block #73,922,833

8 transactions · 8 stateful · 2026-05-11 16:21:48 UTC

Parallelism

75/100

Blocked

13%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,922,833  ·  8 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

0xac8e97a0…8426

0x34b655…2a6f

4 touches
1 conflict

0xee230b20…5a0f

0x34b655…2a6f

4 touches
1 conflict

0x9d92359d…0ca7

0x34b655…2a6f

4 touches
1 conflict

0x1319ae2c…7f9a

0x34b655…2a6f

2 touches
0 conflicts

0x4f483049…3cc7

0x34b655…2a6f

2 touches
0 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

2 touches
0 conflicts

0x77905798…fe3d

0x34b655…2a6f

2 touches
0 conflicts

0x8a85cf3d…2868

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 0xac8e97a09a…ea8426

← previous block·next block →recent activity