Block #72,284,500

← previous blocknext block →recent activity

Analyzing

Block #72,284,500

6 transactions · 4 stateful · 2026-05-04 02:17:03 UTC

Parallelism

67/100

Blocked

25%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,284,500  ·  6 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

0xadac4a86…c2bc

0x34b655…2a6f

4 touches
1 conflict

0xb8228d38…3953

0x34b655…2a6f

4 touches
1 conflict

0x8a51444d…223c

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xa3ff1ab2…8ae3

0x34b655…2a6f

4 touches
1 conflict

0x24d866cf…b001

0x065c9d…c394

2 touches
0 conflicts

0xef0fac16…46bc

0x065c9d…c394

2 touches
0 conflicts

0x4db74a88…1c46

0x34b655…2a6f

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: 0x34b6552d…112a6f

1 conflict on slot 0xadac4a860c…a3c2bc

← previous block·next block →recent activity