Block #72,399,633

← previous blocknext block →recent activity

Analyzing

Block #72,399,633

9 transactions · 6 stateful · 2026-05-04 15:04:46 UTC

Parallelism

78/100

Blocked

17%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xbb8a814f…af11

0x065c9d…c394

4 touches
1 conflict

0x5aaf8266…0297

0x065c9d…c394

3 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

2 touches
0 conflicts

0x336ba317…8686

0x065c9d…c394

2 touches
0 conflicts

0x371e11bc…a226

0x065c9d…c394

2 touches
0 conflicts

0x3ab10e68…ac3c

0x065c9d…c394

2 touches
0 conflicts

0x422f8d95…ed0b

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