Block #73,383,599

← previous blocknext block →recent activity

Analyzing

Block #73,383,599

20 transactions · 14 stateful · 2026-05-09 04:16:42 UTC

Parallelism

70/100

Blocked

50%

Avg conflicts / tx

0.9

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,383,599  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xb393cc70…b7cc

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…0003

0xf4e40a…28ea

6 touches
3 conflicts

0x00000000…002e

0x1b6862…e19c

6 touches
3 conflicts

0x65bd5770…5ed0

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0xd352f775…a505

0x39b9e0…7777

6 touches
3 conflicts

0xfcdba3b0…cfc2

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0000

0xf4e40a…28ea

6 touches
3 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

15 conflicts on slot 0xb393cc70d1…acb7cc

← previous block·next block →recent activity