Block #72,314,915

← previous blocknext block →recent activity

Analyzing

Block #72,314,915

14 transactions · 12 stateful · 2026-05-04 05:40:18 UTC

Parallelism

86/100

Blocked

8%

Avg conflicts / tx

0.07

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,314,915  ·  14 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

0xb9d2cf20…a668

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xeea145a0…067b

0x34b655…2a6f

4 touches
1 conflict

0xfe3b9476…2e67

0x34b655…2a6f

4 touches
1 conflict

0x97b0b2ee…4666

0x34b655…2a6f

4 touches
1 conflict

0xa92c8763…6d7f

0x34b655…2a6f

4 touches
1 conflict

0x8b61b036…1f0c

0x065c9d…c394

2 touches
0 conflicts

0x8c001fa3…9d13

0x065c9d…c394

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 0xb9d2cf2005…28a668

← previous block·next block →recent activity