← previous blocknext block →recent activity

Analyzing

Block #73,035,168

39 transactions · 32 stateful · 2026-05-07 13:38:35 UTC

Parallelism

77/100

Blocked

66%

Avg conflicts / tx

2.03

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,035,168  ·  39 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

0x407dafa1…ab65

0xd32edf…ff58

17 touches
36 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0x00000000…0015

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…001f

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…002f

0x1b6862…e19c

12 touches
15 conflicts

0x3af0dd8e…0028

0x1b6862…e19c

12 touches
15 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

12 touches
15 conflicts

0x388e001a…7e04

0x34b655…2a6f

12 touches
15 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

36 conflicts on slot 0x407dafa1dd…8bab65

← previous block·next block →recent activity