← previous blocknext block →recent activity

Analyzing

Block #72,285,738

15 transactions · 13 stateful · 2026-05-04 02:25:24 UTC

Parallelism

67/100

Blocked

54%

Avg conflicts / tx

1.33

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,285,738  ·  15 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x92d610a6…9a40

0x2a68ba…90c5

10 touches
10 conflicts

0xc53344ee…a966

0xd32edf…ff58

9 touches
10 conflicts

0x0355a908…cf79

0x065c9d…c394

7 touches
6 conflicts

0x56a919c4…ab49

0xee8c0e…1242

4 touches
1 conflict

0x12309510…0ac2

0x000000…012a

4 touches
1 conflict

0x335a161d…fe7f

0x000000…012a

4 touches
1 conflict

0x729c91b8…9537

0x188d58…ea8e

4 touches
1 conflict

0x729c91b8…9539

0x188d58…ea8e

4 touches
1 conflict

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: 0x2a68ba18…8e90c5

10 conflicts on slot 0x92d610a6f9…379a40

← previous block·next block →recent activity