← previous blocknext block →recent activity

Analyzing

Block #72,267,337

22 transactions · 17 stateful · 2026-05-04 00:21:42 UTC

Parallelism

68/100

Blocked

59%

Avg conflicts / tx

1.27

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #72,267,337  ·  22 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

0x46b369fd…c1a4

0xd32edf…ff58

13 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0018

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0028

0x1b6862…e19c

4 touches
1 conflict

0x6aa624fd…a84b

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

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 0x46b369fde1…7fc1a4

← previous block·next block →recent activity