Block #72,284,470

← previous blocknext block →recent activity

Analyzing

Block #72,284,470

20 transactions · 19 stateful · 2026-05-04 02:16:51 UTC

Parallelism

85/100

Blocked

11%

Avg conflicts / tx

0.15

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,284,470  ·  20 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xbbee74c2…567a

0x065c9d…c394

4 touches
1 conflict

0x24cc7fc7…fa3a

0x065c9d…c394

3 touches
1 conflict

0x6d9f0aa9…2cf2

0x065c9d…c394

3 touches
1 conflict

0x8ce813fe…b7db

0x065c9d…c394

3 touches
1 conflict

0x74e71984…ae90

0x2a68ba…90c5

2 touches
0 conflicts

0x2b36ecc6…093e

0x3c2269…cf62

2 touches
0 conflicts

0x3bf71d3d…602c

0x3c2269…cf62

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity