Block #73,706,325

← previous blocknext block →recent activity

Analyzing

Block #73,706,325

20 transactions · 16 stateful · 2026-05-10 16:11:08 UTC

Parallelism

80/100

Blocked

44%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,706,325  ·  20 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x2722623f…0637

0xd32edf…ff58

7 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x0ac31945…2c72

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xaa8a1c54…ead3

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

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: 0xd32edf66…9fff58

6 conflicts on slot 0x2722623f63…de0637

← previous block·next block →recent activity