← previous blocknext block →recent activity

Analyzing

Block #72,400,220

19 transactions · 13 stateful · 2026-05-04 15:08:41 UTC

Parallelism

74/100

Blocked

62%

Avg conflicts / tx

0.74

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,400,220  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

8 touches
6 conflicts

0x8a35acfb…d1ae

0x8d66a4…3095

6 touches
3 conflicts

0xbad68552…e6bf

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x888660ec…c3eb

0x34b655…2a6f

4 touches
1 conflict

0x97ab5020…3f1b

0x34b655…2a6f

4 touches
1 conflict

0xa2e5fc54…2105

0x34b655…2a6f

4 touches
1 conflict

0xa9988419…9f45

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

6 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity