Block #72,399,517

← previous blocknext block →recent activity

Analyzing

Block #72,399,517

55 transactions · 32 stateful · 2026-05-04 15:04:00 UTC

Parallelism

75/100

Blocked

56%

Avg conflicts / tx

1.36

Longest chain

14 deep

Execution timeline

did this block parallelize well?

view

block #72,399,517  ·  55 txs across 14 waves  ·  depth 14
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

wave w13

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

0x60f7fbaf…bd58

0x34b655…2a6f

18 touches
36 conflicts

0xc824469a…6425

0x34b655…2a6f

14 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xbe9d1d23…3de2

0x34b655…2a6f

10 touches
10 conflicts

0x24968e6d…0132

0x065c9d…c394

8 touches
6 conflicts

0x51087f5a…61f7

0x34b655…2a6f

8 touches
6 conflicts

0x95e5ee51…5e3e

0x34b655…2a6f

8 touches
6 conflicts

0xbad68552…e6bf

0x34b655…2a6f

8 touches
6 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: 0x34b6552d…112a6f

36 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity