← previous blocknext block →recent activity

Analyzing

Block #72,817,337

15 transactions · 14 stateful · 2026-05-06 13:28:13 UTC

Parallelism

67/100

Blocked

36%

Avg conflicts / tx

0.53

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,817,337  ·  15 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

6 touches
3 conflicts

0xb7af7ea3…7d7d

0x34b655…2a6f

6 touches
3 conflicts

0xe96c91d2…32ff

0x8d66a4…3095

4 touches
1 conflict

0x47c1a8e8…f74a

0x34b655…2a6f

4 touches
1 conflict

0x520d9da3…2b7f

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x8a35acfb…d1ad

0x8d66a4…3095

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 0x60f7fbaf90…97bd58

← previous block·next block →recent activity