← previous blocknext block →recent activity

Analyzing

Block #73,374,005

19 transactions · 13 stateful · 2026-05-09 03:12:55 UTC

Parallelism

53/100

Blocked

62%

Avg conflicts / tx

1.89

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,374,005  ·  19 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

0x89676bee…abec

0xd32edf…ff58

17 touches
36 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001e

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002e

0x1b6862…e19c

4 touches
1 conflict

0xba5743c7…21c5

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 0x89676bee4f…3aabec

← previous block·next block →recent activity