Block #72,496,193

← previous blocknext block →recent activity

Analyzing

Block #72,496,193

16 transactions · 14 stateful · 2026-05-05 01:47:54 UTC

Parallelism

69/100

Blocked

43%

Avg conflicts / tx

0.75

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,496,193  ·  16 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

10 touches
10 conflicts

0x00000000…0004

0x8d66a4…3095

8 touches
6 conflicts

0x8a35acfb…d1a5

0x8d66a4…3095

7 touches
6 conflicts

0x0520da1d…c88e

0x34b655…2a6f

6 touches
3 conflicts

0x8a35acfb…d1a6

0x8d66a4…3095

5 touches
3 conflicts

0x7f430e47…4cbd

0x8d66a4…3095

5 touches
3 conflicts

0x4a320f8b…2baf

0x34b655…2a6f

4 touches
1 conflict

0x65e795ca…0320

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

10 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity