Block #72,399,230

← previous blocknext block →recent activity

Analyzing

Block #72,399,230

25 transactions · 21 stateful · 2026-05-04 15:02:05 UTC

Parallelism

56/100

Blocked

62%

Avg conflicts / tx

2.32

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #72,399,230  ·  25 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x00000000…0002

0x7e9d3a…9fda

22 touches
55 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xe96c91d2…32ff

0x8d66a4…3095

4 touches
1 conflict

0xbad68552…e6bf

0x34b655…2a6f

4 touches
1 conflict

0xbb1747e2…f78b

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x8a35acfb…d1a6

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1ab

0x8d66a4…3095

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: 0x7e9d3a8a…4f9fda

55 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity