Block #72,284,419

← previous blocknext block →recent activity

Analyzing

Block #72,284,419

12 transactions · 11 stateful · 2026-05-04 02:16:31 UTC

Parallelism

83/100

Blocked

9%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,284,419  ·  12 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

0xcf20f12d…4db4

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x8a8678b8…384a

0x065c9d…c394

4 touches
1 conflict

0x4fee1bbb…53a7

0x065c9d…c394

3 touches
1 conflict

0x8e97cb0a…17a0

0x065c9d…c394

3 touches
1 conflict

0xc801c9d6…e7e2

0x065c9d…c394

3 touches
1 conflict

0x68faa0b9…14af

0x368ee5…7ca4

2 touches
0 conflicts

0xcd621226…2df8

0x368ee5…7ca4

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: 0x065c9d28…a9c394

1 conflict on slot 0xcf20f12d1e…7b4db4

← previous block·next block →recent activity