Block #73,609,802

← previous blocknext block →recent activity

Analyzing

Block #73,609,802

15 transactions · 12 stateful · 2026-05-10 05:21:10 UTC

Parallelism

60/100

Blocked

58%

Avg conflicts / tx

1.27

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,609,802  ·  15 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

0xc9e97522…3519

0x2a68ba…90c5

10 touches
10 conflicts

0xa1087a5c…66c4

0x754704…b603

10 touches
10 conflicts

0x6f08361d…bda6

0x065c9d…c394

6 touches
3 conflicts

0x53293b64…aeb1

0xd32edf…ff58

5 touches
3 conflicts

0x6d12eddf…25d3

0x065c9d…c394

5 touches
3 conflicts

0x82dabf2c…9a94

0x065c9d…c394

5 touches
3 conflicts

0x00000000…0003

0x63e48b…53f2

4 touches
1 conflict

0xeeb8b7fc…24d6

0x6657d1…8ccc

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: 0x2a68ba18…8e90c5

10 conflicts on slot 0xc9e9752290…9c3519

← previous block·next block →recent activity