Block #72,284,386

← previous blocknext block →recent activity

Analyzing

Block #72,284,386

41 transactions · 30 stateful · 2026-05-04 02:16:17 UTC

Parallelism

68/100

Blocked

70%

Avg conflicts / tx

2.27

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #72,284,386  ·  41 txs across 13 waves  ·  depth 13
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

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

0x1762ece4…a271

0xd32edf…ff58

25 touches
78 conflicts

0xea02471d…1542

0x34b655…2a6f

10 touches
10 conflicts

0xbad68552…e6bf

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0018

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0028

0x1b6862…e19c

6 touches
3 conflicts

0x17a7f697…dcb1

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x005fb969…2d97

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

78 conflicts on slot 0x1762ece454…39a271

← previous block·next block →recent activity