← previous blocknext block →recent activity

Analyzing

Block #72,284,253

23 transactions · 20 stateful · 2026-05-04 02:15:23 UTC

Parallelism

87/100

Blocked

25%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,284,253  ·  23 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x7c403af1…31b1

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0004

0xd5b70d…615b

6 touches
3 conflicts

0x00000000…0000

0xd5b70d…615b

6 touches
3 conflicts

0x18aed20c…48f3

0x000000…012a

6 touches
3 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0x00000000…0000

0x63e48b…53f2

4 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: 0x3bd359c1…15433a

3 conflicts on slot 0x7c403af1e6…1d31b1

← previous block·next block →recent activity