← previous blocknext block →recent activity

Analyzing

Block #72,399,137

14 transactions · 9 stateful · 2026-05-04 15:01:28 UTC

Parallelism

86/100

Blocked

22%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,399,137  ·  14 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

0xbad68552…e6bf

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x1c1cefc0…267b

0x065c9d…c394

2 touches
0 conflicts

0x22acc598…60ba

0x065c9d…c394

2 touches
0 conflicts

0x39662e90…e0f6

0x065c9d…c394

2 touches
0 conflicts

0x639f478c…ed77

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

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

1 conflict on slot 0xbad6855239…f0e6bf

← previous block·next block →recent activity