← previous blocknext block →recent activity

Analyzing

Block #72,977,475

13 transactions · 13 stateful · 2026-05-07 07:14:37 UTC

Parallelism

77/100

Blocked

23%

Avg conflicts / tx

0.23

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,977,475  ·  13 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

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x085df2c1…305a

0x34b655…2a6f

2 touches
0 conflicts

0x0eac6378…36f4

0x34b655…2a6f

2 touches
0 conflicts

0x150af51d…9c42

0x34b655…2a6f

2 touches
0 conflicts

0x2c7e5699…a792

0x34b655…2a6f

2 touches
0 conflicts

0x3c35979a…975d

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 0x47c1a8e802…12f74a

← previous block·next block →recent activity