Block #72,283,343

← previous blocknext block →recent activity

Analyzing

Block #72,283,343

18 transactions · 17 stateful · 2026-05-04 02:09:17 UTC

Parallelism

78/100

Blocked

47%

Avg conflicts / tx

0.72

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,283,343  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xbad68552…e6bf

0x34b655…2a6f

8 touches
6 conflicts

0xbbee74c2…567a

0x065c9d…c394

6 touches
3 conflicts

0x005fb969…2d97

0x34b655…2a6f

6 touches
3 conflicts

0x17e2d2a0…359e

0x34b655…2a6f

6 touches
3 conflicts

0x18b81ade…81be

0x34b655…2a6f

6 touches
3 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

6 touches
3 conflicts

0x2877f440…c2c8

0x34b655…2a6f

6 touches
3 conflicts

0x3254d19b…f714

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

6 conflicts on slot 0xbad6855239…f0e6bf

← previous block·next block →recent activity