← previous blocknext block →recent activity

Analyzing

Block #72,856,138

38 transactions · 30 stateful · 2026-05-06 17:47:02 UTC

Parallelism

74/100

Blocked

70%

Avg conflicts / tx

1.76

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #72,856,138  ·  38 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x968c1f23…9713

0xd32edf…ff58

15 touches
28 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0x3b8ffd61…f3ad

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x78e3ec57…8bf9

0x34b655…2a6f

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0xce7c598a…631b

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

28 conflicts on slot 0x968c1f2322…179713

← previous block·next block →recent activity