← previous blocknext block →recent activity

Analyzing

Block #73,695,083

26 transactions · 23 stateful · 2026-05-10 14:55:17 UTC

Parallelism

73/100

Blocked

61%

Avg conflicts / tx

1.31

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,695,083  ·  26 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

0xfde64a46…33c6

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…0002

0xab3526…fa38

8 touches
6 conflicts

0x529acb6a…fcc6

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001c

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002c

0x1b6862…e19c

4 touches
1 conflict

0x14d1bf0e…e09d

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

21 conflicts on slot 0xfde64a464e…1733c6

← previous block·next block →recent activity