Block #73,594,340

← previous blocknext block →recent activity

Analyzing

Block #73,594,340

20 transactions · 16 stateful · 2026-05-10 03:38:18 UTC

Parallelism

65/100

Blocked

56%

Avg conflicts / tx

1.35

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,594,340  ·  20 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x50f01527…af39

0xd32edf…ff58

13 touches
21 conflicts

0xe6455d1f…1029

0x754704…b603

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x0d0b2509…074d

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001a

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002a

0x1b6862…e19c

4 touches
1 conflict

0x4d87512b…897c

0x065c9d…c394

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

21 conflicts on slot 0x50f015278b…2eaf39

← previous block·next block →recent activity