Block #72,399,324

← previous blocknext block →recent activity

Analyzing

Block #72,399,324

7 transactions · 4 stateful · 2026-05-04 15:02:42 UTC

Parallelism

71/100

Blocked

25%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,399,324  ·  7 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x95e5ee51…5e3e

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x8a35acfb…d1ab

0x8d66a4…3095

3 touches
1 conflict

0xe96c91d2…32ff

0x8d66a4…3095

3 touches
1 conflict

0x39e56c78…9be2

0x065c9d…c394

2 touches
0 conflicts

0x7fad2745…2b31

0x065c9d…c394

2 touches
0 conflicts

0x8f92dcf0…caf2

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

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

1 conflict on slot 0x95e5ee5137…105e3e

← previous block·next block →recent activity