← previous blocknext block →recent activity

Analyzing

Block #72,497,044

26 transactions · 19 stateful · 2026-05-05 01:53:34 UTC

Parallelism

73/100

Blocked

47%

Avg conflicts / tx

0.73

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #72,497,044  ·  26 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

0x9e343d65…2c3f

0xd32edf…ff58

9 touches
10 conflicts

0xf91b744e…9117

0x754704…b603

6 touches
3 conflicts

0xcad937e9…7870

0x1b6862…e19c

6 touches
3 conflicts

0x6af306bb…2e81

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x1c354dc0…96de

0x754704…b603

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

10 conflicts on slot 0x9e343d65ac…922c3f

← previous block·next block →recent activity