Block #73,396,716

← previous blocknext block →recent activity

Analyzing

Block #73,396,716

18 transactions · 17 stateful · 2026-05-09 05:44:02 UTC

Parallelism

50/100

Blocked

59%

Avg conflicts / tx

2.22

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,396,716  ·  18 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x30e32eb5…6486

0xd32edf…ff58

17 touches
36 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x1045386d…cb8c

0x1b6862…e19c

6 touches
3 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0xd0baba36…0681

0x065c9d…c394

5 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

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

36 conflicts on slot 0x30e32eb5a1…136486

← previous block·next block →recent activity