← previous blocknext block →recent activity

Analyzing

Block #72,979,719

14 transactions · 10 stateful · 2026-05-07 07:29:31 UTC

Parallelism

79/100

Blocked

20%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,979,719  ·  14 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x4e5ebbf7…ae70

0xc8689a…ee79

6 touches
3 conflicts

0x0175b7a6…1db9

0x6ca43f…c331

6 touches
3 conflicts

0x0175b7a6…1dba

0x6ca43f…c331

6 touches
3 conflicts

0x0175b7a6…1dbb

0x6ca43f…c331

6 touches
3 conflicts

0x0175b7a6…1dbd

0x6ca43f…c331

6 touches
3 conflicts

0x1a4b4152…0a08

0x6ca43f…c331

6 touches
3 conflicts

0x3e4b8d9f…b8a7

0x6ca43f…c331

6 touches
3 conflicts

0x5b3dfef8…a676

0x6ca43f…c331

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: 0xc8689a47…62ee79

3 conflicts on slot 0x4e5ebbf7fb…3fae70

← previous block·next block →recent activity