Block #72,496,964

← previous blocknext block →recent activity

Analyzing

Block #72,496,964

15 transactions · 14 stateful · 2026-05-05 01:53:03 UTC

Parallelism

73/100

Blocked

50%

Avg conflicts / tx

0.87

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,496,964  ·  15 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

0xf3981be5…2c47

0x34b655…2a6f

8 touches
6 conflicts

0xee1a266d…dc55

0xd32edf…ff58

7 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xcafa2040…d440

0x34b655…2a6f

4 touches
1 conflict

0xc3c8642a…7da5

0x2a68ba…90c5

4 touches
1 conflict

0x0f28fb99…3d2d

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

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 0xf3981be56e…f02c47

← previous block·next block →recent activity