Block #72,430,159

← previous blocknext block →recent activity

Analyzing

Block #72,430,159

13 transactions · 11 stateful · 2026-05-04 18:28:08 UTC

Parallelism

85/100

Blocked

18%

Avg conflicts / tx

0.15

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,430,159  ·  13 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

0xb6b74ae0…8d5e

0xea1b8e…c5ec

4 touches
1 conflict

0x00bac013…a28c

0xfd44b3…00d1

4 touches
1 conflict

0x1a606974…71ae

0x065c9d…c394

2 touches
0 conflicts

0x266eddd3…d362

0x065c9d…c394

2 touches
0 conflicts

0x4d10233a…94a3

0x065c9d…c394

2 touches
0 conflicts

0x52363343…1cf5

0x065c9d…c394

2 touches
0 conflicts

0x5c01350e…ff57

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