Block #72,301,087

← previous blocknext block →recent activity

Analyzing

Block #72,301,087

5 transactions · 3 stateful · 2026-05-04 04:08:12 UTC

Parallelism

60/100

Blocked

33%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,301,087  ·  5 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

0xa87f4ae3…8308

0x065c9d…c394

4 touches
1 conflict

0x4c5de40f…e7f5

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xa708f77b…ff5e

0x065c9d…c394

4 touches
1 conflict

0x8da4e2b9…2a09

0x065c9d…c394

3 touches
1 conflict

0x4b1a1096…07d0

0x065c9d…c394

3 touches
1 conflict

0x1c9cbb7f…e5c6

0x065c9d…c394

3 touches
1 conflict

0x9f758efc…82bd

0x065c9d…c394

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

1 conflict on slot 0xa87f4ae3b2…b68308

← previous block·next block →recent activity