Block #73,211,510

← previous blocknext block →recent activity

Analyzing

Block #73,211,510

6 transactions · 6 stateful · 2026-05-08 09:11:54 UTC

Parallelism

67/100

Blocked

17%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,211,510  ·  6 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

0x746bcce3…d0ce

0x34b655…2a6f

4 touches
1 conflict

0x943e9fce…3cdb

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x0dbb4745…3b18

0x34b655…2a6f

4 touches
1 conflict

0x53c41998…7d52

0x34b655…2a6f

3 touches
1 conflict

0xcb45d9d6…cb83

0x1b6862…e19c

2 touches
0 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

2 touches
0 conflicts

0x8876d94c…8435

0x2a68ba…90c5

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 0x746bcce3fa…c7d0ce

← previous block·next block →recent activity