Block #72,224,858

← previous blocknext block →recent activity

Analyzing

Block #72,224,858

21 transactions · 14 stateful · 2026-05-03 19:36:10 UTC

Parallelism

71/100

Blocked

36%

Avg conflicts / tx

0.48

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,224,858  ·  21 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

0xc1a4c088…e828

0x34b655…2a6f

8 touches
6 conflicts

0xa02838a3…bc54

0x34b655…2a6f

8 touches
6 conflicts

0xfa2527aa…9dd5

0x34b655…2a6f

6 touches
3 conflicts

0x35b65947…44d1

0xc8689a…ee79

6 touches
3 conflicts

0x473d914d…d1d7

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x65e795ca…0320

0x34b655…2a6f

6 touches
3 conflicts

0x773ae084…6b9d

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 0xc1a4c08897…f9e828

← previous block·next block →recent activity