Block #72,496,630

← previous blocknext block →recent activity

Analyzing

Block #72,496,630

12 transactions · 10 stateful · 2026-05-05 01:50:49 UTC

Parallelism

67/100

Blocked

30%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,496,630  ·  12 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0x257251ca…49b8

0x34b655…2a6f

6 touches
3 conflicts

0x578e7f66…1b56

0x34b655…2a6f

4 touches
1 conflict

0x6d0c65d9…c36f

0x34b655…2a6f

4 touches
1 conflict

0x77905798…fe3d

0x34b655…2a6f

4 touches
1 conflict

0x3eadb0b6…d2f7

0x34b655…2a6f

4 touches
1 conflict

0xb378025c…30cf

0x34b655…2a6f

4 touches
1 conflict

0xf853eb8e…4027

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity