Block #73,499,763

← previous blocknext block →recent activity

Analyzing

Block #73,499,763

21 transactions · 18 stateful · 2026-05-09 17:09:49 UTC

Parallelism

57/100

Blocked

50%

Avg conflicts / tx

1.81

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,499,763  ·  21 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

0x00000000…0002

0xab3526…fa38

18 touches
36 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x15c9b5bf…f732

0x34b655…2a6f

2 touches
0 conflicts

0x207fb267…de78

0x34b655…2a6f

2 touches
0 conflicts

0x2484cc15…5afc

0x34b655…2a6f

2 touches
0 conflicts

0x3b9e61ad…a20d

0x34b655…2a6f

2 touches
0 conflicts

0x43e1ca5e…b685

0x34b655…2a6f

2 touches
0 conflicts

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: 0xab35264b…1cfa38

36 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity