Block #72,399,535

← previous blocknext block →recent activity

Analyzing

Block #72,399,535

22 transactions · 20 stateful · 2026-05-04 15:04:07 UTC

Parallelism

50/100

Blocked

60%

Avg conflicts / tx

2.64

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #72,399,535  ·  22 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x00000000…0002

0x7e9d3a…9fda

22 touches
55 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…0006

0x2ab50b…5c41

2 touches
0 conflicts

0x039fd5ab…0d4f

0x2ab50b…5c41

2 touches
0 conflicts

0x05b8ccbb…46bc

0x2ab50b…5c41

2 touches
0 conflicts

0x0ffd9cbf…f9c5

0x2ab50b…5c41

2 touches
0 conflicts

0x134bb1e3…b524

0x2ab50b…5c41

2 touches
0 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: 0x7e9d3a8a…4f9fda

55 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity