Block #72,366,099

← previous blocknext block →recent activity

Analyzing

Block #72,366,099

21 transactions · 17 stateful · 2026-05-04 11:21:15 UTC

Parallelism

76/100

Blocked

53%

Avg conflicts / tx

1.1

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,366,099  ·  21 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

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x736c5b69…fb3f

0x34b655…2a6f

8 touches
6 conflicts

0x35b85d8e…1edd

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x8a35acfb…d1ae

0x8d66a4…3095

6 touches
3 conflicts

0x8d7ae453…cbe1

0x34b655…2a6f

4 touches
1 conflict

0x98a482a9…0f92

0x34b655…2a6f

4 touches
1 conflict

0x10f5f4d8…572e

0x34b655…2a6f

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

10 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity