Block #72,399,793

← previous blocknext block →recent activity

Analyzing

Block #72,399,793

13 transactions · 9 stateful · 2026-05-04 15:05:50 UTC

Parallelism

77/100

Blocked

33%

Avg conflicts / tx

0.23

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,399,793  ·  13 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0xd64a493a…459e

0xd32edf…ff58

3 touches
1 conflict

0x4ba1fda1…2acc

0x065c9d…c394

2 touches
0 conflicts

0x6549da7a…6602

0x065c9d…c394

2 touches
0 conflicts

0x7abf1904…b003

0x065c9d…c394

2 touches
0 conflicts

0xb0084534…b41a

0x065c9d…c394

2 touches
0 conflicts

0xf582609d…a506

0x065c9d…c394

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: 0x065c9d28…a9c394

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity