← previous blocknext block →recent activity

Analyzing

Block #72,979,400

12 transactions · 12 stateful · 2026-05-07 07:27:25 UTC

Parallelism

75/100

Blocked

42%

Avg conflicts / tx

0.58

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,979,400  ·  12 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

0x47c1a8e8…f74a

0x34b655…2a6f

6 touches
3 conflicts

0x68cef7be…4a38

0xd32edf…ff58

5 touches
3 conflicts

0x085df2c1…305a

0x34b655…2a6f

4 touches
1 conflict

0x3c35979a…975d

0x34b655…2a6f

4 touches
1 conflict

0x414e9446…4b59

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x65e795ca…0320

0x34b655…2a6f

4 touches
1 conflict

0x8aa1941d…2988

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

3 conflicts on slot 0x47c1a8e802…12f74a

← previous block·next block →recent activity