Block #73,210,770

← previous blocknext block →recent activity

Analyzing

Block #73,210,770

24 transactions · 19 stateful · 2026-05-08 09:07:00 UTC

Parallelism

79/100

Blocked

42%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,210,770  ·  24 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x00000000…0002

0xab3526…fa38

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x37cfaf01…4a46

0x34b655…2a6f

8 touches
6 conflicts

0x6eba5e7f…4b52

0x34b655…2a6f

6 touches
3 conflicts

0x388e001a…7e04

0x34b655…2a6f

6 touches
3 conflicts

0xa7a586ac…c700

0x34b655…2a6f

6 touches
3 conflicts

0xb96e29a5…0419

0x34b655…2a6f

6 touches
3 conflicts

0x4a03ceb5…a07f

0x34b655…2a6f

4 touches
1 conflict

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: 0xab35264b…1cfa38

10 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity