Block #72,859,463

← previous blocknext block →recent activity

Analyzing

Block #72,859,463

10 transactions · 10 stateful · 2026-05-06 18:09:09 UTC

Parallelism

70/100

Blocked

20%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,859,463  ·  10 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x9e0e23b5…6910

0x34b655…2a6f

4 touches
1 conflict

0xe70f6c1d…2539

0x34b655…2a6f

4 touches
1 conflict

0x9fe14cdc…05ef

0x34b655…2a6f

2 touches
0 conflicts

0xa9988419…9f45

0x34b655…2a6f

2 touches
0 conflicts

0xc4d8b6d3…c241

0x34b655…2a6f

2 touches
0 conflicts

0xd895ee0b…d301

0x34b655…2a6f

2 touches
0 conflicts

0xd8cadc0d…776e

0x34b655…2a6f

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity