Block #72,213,489

← previous blocknext block →recent activity

Analyzing

Block #72,213,489

10 transactions · 8 stateful · 2026-05-03 18:19:52 UTC

Parallelism

80/100

Blocked

13%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,213,489  ·  10 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

0x8a35acfb…d1ab

0x8d66a4…3095

4 touches
1 conflict

0x96504a63…52d2

0x8d66a4…3095

4 touches
1 conflict

0x15c9b5bf…f732

0x34b655…2a6f

2 touches
0 conflicts

0x16706b1f…c22b

0x34b655…2a6f

2 touches
0 conflicts

0x2484cc15…5afc

0x34b655…2a6f

2 touches
0 conflicts

0x364a100f…7f6b

0x34b655…2a6f

2 touches
0 conflicts

0x3b9e61ad…a20d

0x34b655…2a6f

2 touches
0 conflicts

0x58728085…d586

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: 0x8d66a43f…113095

1 conflict on slot 0x8a35acfbc1…6bd1ab

← previous block·next block →recent activity