Block #72,860,107

← previous blocknext block →recent activity

Analyzing

Block #72,860,107

24 transactions · 22 stateful · 2026-05-06 18:13:26 UTC

Parallelism

67/100

Blocked

64%

Avg conflicts / tx

1.54

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #72,860,107  ·  24 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x4792532b…86eb

0xd32edf…ff58

9 touches
10 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x874cb67f…26de

0x1b6862…e19c

6 touches
3 conflicts

0x8a35acfb…d1ac

0x8d66a4…3095

6 touches
3 conflicts

0xe89e1a22…ce49

0x8d66a4…3095

6 touches
3 conflicts

0x70b2f813…783c

0x2a68ba…90c5

6 touches
3 conflicts

0x0de7749d…5bef

0x34b655…2a6f

6 touches
3 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: 0x34b6552d…112a6f

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity