Block #72,283,146

← previous blocknext block →recent activity

Analyzing

Block #72,283,146

28 transactions · 21 stateful · 2026-05-04 02:07:56 UTC

Parallelism

79/100

Blocked

52%

Avg conflicts / tx

0.86

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,283,146  ·  28 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x9ae9d135…fab6

0xd32edf…ff58

11 touches
15 conflicts

0x4db74a88…1c46

0x34b655…2a6f

6 touches
3 conflicts

0xbad68552…e6bf

0x34b655…2a6f

6 touches
3 conflicts

0xdfda089f…747f

0x3bd359…433a

6 touches
3 conflicts

0x17e2d2a0…359e

0x34b655…2a6f

4 touches
1 conflict

0x18b81ade…81be

0x34b655…2a6f

4 touches
1 conflict

0x1b5d2e60…99b5

0x34b655…2a6f

4 touches
1 conflict

0x2877f440…c2c8

0x34b655…2a6f

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

15 conflicts on slot 0x9ae9d1353a…35fab6

← previous block·next block →recent activity