Block #72,284,393

← previous blocknext block →recent activity

Analyzing

Block #72,284,393

17 transactions · 15 stateful · 2026-05-04 02:16:20 UTC

Parallelism

65/100

Blocked

33%

Avg conflicts / tx

0.47

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,284,393  ·  17 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

6 touches
3 conflicts

0xea01f4fd…4442

0xd32edf…ff58

5 touches
3 conflicts

0xd0ec60a1…d240

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x0222aacd…670e

0x065c9d…c394

3 touches
1 conflict

0xb81a6956…f7ca

0xa6afd3…d132

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity