← previous blocknext block →recent activity

Analyzing

Block #72,284,747

25 transactions · 21 stateful · 2026-05-04 02:18:42 UTC

Parallelism

76/100

Blocked

43%

Avg conflicts / tx

0.88

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,284,747  ·  25 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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xb8228d38…3953

0x34b655…2a6f

6 touches
3 conflicts

0x02bfdbf9…6514

0x34b655…2a6f

6 touches
3 conflicts

0x2514957e…660a

0x34b655…2a6f

4 touches
1 conflict

0x36532fee…58e4

0x34b655…2a6f

4 touches
1 conflict

0x5a84bc4a…9de1

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x664bf99e…0a8c

0x34b655…2a6f

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity