Block #72,283,421

← previous blocknext block →recent activity

Analyzing

Block #72,283,421

16 transactions · 14 stateful · 2026-05-04 02:09:48 UTC

Parallelism

69/100

Blocked

29%

Avg conflicts / tx

0.63

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,283,421  ·  16 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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xeebd31ac…0794

0x34b655…2a6f

6 touches
3 conflicts

0x49339736…b223

0x34b655…2a6f

6 touches
3 conflicts

0x59ef13ba…2741

0x34b655…2a6f

6 touches
3 conflicts

0x8f375dda…1b11

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xcf17589f…048c

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity