← previous blocknext block →recent activity

Analyzing

Block #72,288,062

44 transactions · 26 stateful · 2026-05-04 02:41:02 UTC

Parallelism

86/100

Blocked

54%

Avg conflicts / tx

0.7

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,288,062  ·  44 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0xbb1747e2…f78b

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1ac

0x8d66a4…3095

8 touches
6 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x44384aad…ee45

0xd32edf…ff58

5 touches
3 conflicts

0x143dba04…1b98

0x8d66a4…3095

4 touches
1 conflict

0x1e451306…7993

0x8d66a4…3095

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

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: 0x34b6552d…112a6f

15 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity