← previous blocknext block →recent activity

Analyzing

Block #73,212,041

37 transactions · 29 stateful · 2026-05-08 09:15:23 UTC

Parallelism

84/100

Blocked

52%

Avg conflicts / tx

1.08

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,212,041  ·  37 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x50abd4b2…47b5

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001b

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002b

0x1b6862…e19c

8 touches
6 conflicts

0xf4730a2d…3538

0x34b655…2a6f

8 touches
6 conflicts

0xab2a87f1…eafe

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

15 conflicts on slot 0x50abd4b238…7247b5

← previous block·next block →recent activity