← previous blocknext block →recent activity

Analyzing

Block #73,811,520

36 transactions · 26 stateful · 2026-05-11 04:00:17 UTC

Parallelism

81/100

Blocked

62%

Avg conflicts / tx

1.25

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,811,520  ·  36 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

0x298db80a…ac98

0xd32edf…ff58

13 touches
21 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x8240d70c…7c3b

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…001f

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002f

0x1b6862…e19c

8 touches
6 conflicts

0x45364cf9…65d8

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 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: 0xd32edf66…9fff58

21 conflicts on slot 0x298db80ab2…72ac98

← previous block·next block →recent activity