← previous blocknext block →recent activity

Analyzing

Block #72,300,790

8 transactions · 7 stateful · 2026-05-04 04:06:14 UTC

Parallelism

75/100

Blocked

14%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,300,790  ·  8 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

0x4f4bdabd…ffba

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xffedaa84…311b

0x34b655…2a6f

4 touches
1 conflict

0x10f5f4d8…572e

0x34b655…2a6f

2 touches
0 conflicts

0x1608635c…d25d

0x34b655…2a6f

2 touches
0 conflicts

0x2484cc15…5afc

0x34b655…2a6f

2 touches
0 conflicts

0x2fc166fd…c38a

0x34b655…2a6f

2 touches
0 conflicts

0x336241b2…c1db

0x34b655…2a6f

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 0x4f4bdabdf3…ecffba

← previous block·next block →recent activity