Block #72,976,076

← previous blocknext block →recent activity

Analyzing

Block #72,976,076

19 transactions · 17 stateful · 2026-05-07 07:05:17 UTC

Parallelism

63/100

Blocked

59%

Avg conflicts / tx

0.95

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #72,976,076  ·  19 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x6a6caf45…b19e

0xd32edf…ff58

7 touches
6 conflicts

0x55968d29…1d6a

0x34b655…2a6f

6 touches
3 conflicts

0x79e405c3…815f

0x34b655…2a6f

6 touches
3 conflicts

0xb91a6f59…722c

0x34b655…2a6f

6 touches
3 conflicts

0xc9766ad0…a0f4

0x34b655…2a6f

6 touches
3 conflicts

0xdaca243a…f9de

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

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: 0xd32edf66…9fff58

6 conflicts on slot 0x6a6caf45b0…51b19e

← previous block·next block →recent activity