Block #72,496,185

← previous blocknext block →recent activity

Analyzing

Block #72,496,185

10 transactions · 8 stateful · 2026-05-05 01:47:51 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,496,185  ·  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

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x729c91b8…9538

0x188d58…ea8e

4 touches
1 conflict

0x729c91b8…9537

0x188d58…ea8e

4 touches
1 conflict

0x56a919c4…ab49

0xee8c0e…1242

4 touches
1 conflict

0x00f7e3b7…e016

0x188d58…ea8e

2 touches
0 conflicts

0x968bdacb…f461

0x2a68ba…90c5

2 touches
0 conflicts

0xa4e3b3b1…0911

0x2a68ba…90c5

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: 0x754704bc…afb603

1 conflict on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity