Block #72,301,178

← previous blocknext block →recent activity

Analyzing

Block #72,301,178

13 transactions · 10 stateful · 2026-05-04 04:08:49 UTC

Parallelism

85/100

Blocked

10%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,301,178  ·  13 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

0x388f889f…a655

0x34b655…2a6f

4 touches
1 conflict

0xa3ff1ab2…8ae3

0x34b655…2a6f

4 touches
1 conflict

0xb8228d38…3953

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf06c2cf5…61bd

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

2 touches
0 conflicts

0x280fc211…69e9

0x754704…b603

2 touches
0 conflicts

0xe6ca9db5…faa2

0x754704…b603

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 0x388f889f28…0aa655

← previous block·next block →recent activity