Block #72,267,095

← previous blocknext block →recent activity

Analyzing

Block #72,267,095

12 transactions · 11 stateful · 2026-05-04 00:20:05 UTC

Parallelism

67/100

Blocked

36%

Avg conflicts / tx

0.58

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,267,095  ·  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

0x00000000…0002

0x7e9d3a…9fda

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xe8a23666…5f87

0x065c9d…c394

4 touches
1 conflict

0xbc1c25bb…9fe9

0x065c9d…c394

3 touches
1 conflict

0x17f75edf…9b03

0x065c9d…c394

2 touches
0 conflicts

0x41755291…977f

0x065c9d…c394

2 touches
0 conflicts

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0x5809da19…8f28

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

6 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity