← previous blocknext block →recent activity

Analyzing

Block #72,271,409

9 transactions · 7 stateful · 2026-05-04 00:49:05 UTC

Parallelism

78/100

Blocked

29%

Avg conflicts / tx

0.22

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,271,409  ·  9 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x485d2778…aa5a

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0018

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0028

0x1b6862…e19c

4 touches
1 conflict

0x379cf9a8…f0fa

0x065c9d…c394

4 touches
1 conflict

0x49bad189…6264

0x065c9d…c394

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: 0x1b68626d…2de19c

1 conflict on slot 0x485d277847…5daa5a

← previous block·next block →recent activity