Block #73,744,557

← previous blocknext block →recent activity

Analyzing

Block #73,744,557

23 transactions · 17 stateful · 2026-05-10 20:29:09 UTC

Parallelism

78/100

Blocked

41%

Avg conflicts / tx

0.7

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,744,557  ·  23 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x529acb6a…fcc6

0x065c9d…c394

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xae69c125…2379

0x2a68ba…90c5

6 touches
3 conflicts

0x0056ec18…0350

0xd32edf…ff58

5 touches
3 conflicts

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…000b

0x6c4bfa…a540

4 touches
1 conflict

0x0175b7a6…1db9

0x6c4bfa…a540

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: 0x065c9d28…a9c394

10 conflicts on slot 0x529acb6ad1…f0fcc6

← previous block·next block →recent activity