Block #72,859,567

← previous blocknext block →recent activity

Analyzing

Block #72,859,567

38 transactions · 31 stateful · 2026-05-06 18:09:50 UTC

Parallelism

79/100

Blocked

58%

Avg conflicts / tx

1.37

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #72,859,567  ·  38 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x7e4b03da…6d07

0xd32edf…ff58

13 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xf853eb8e…4027

0x34b655…2a6f

10 touches
10 conflicts

0x388e001a…7e04

0x34b655…2a6f

10 touches
10 conflicts

0x78e3ec57…8bf9

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x36cdae67…8407

0x34b655…2a6f

8 touches
6 conflicts

0xbc04d98e…a484

0x34b655…2a6f

6 touches
3 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 0x7e4b03da1e…506d07

← previous block·next block →recent activity