← previous blocknext block →recent activity

Analyzing

Block #72,976,333

13 transactions · 11 stateful · 2026-05-07 07:07:01 UTC

Parallelism

62/100

Blocked

45%

Avg conflicts / tx

0.92

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,976,333  ·  13 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xf91b744e…9117

0x754704…b603

10 touches
10 conflicts

0x6af306bb…2e81

0x3bd359…433a

10 touches
10 conflicts

0x1c354dc0…96de

0x754704…b603

10 touches
10 conflicts

0xcb45d9d6…cb86

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001e

0x1b6862…e19c

8 touches
6 conflicts

0x5d3285af…ccd2

0xd32edf…ff58

7 touches
6 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

10 conflicts on slot 0xf91b744ece…1a9117

← previous block·next block →recent activity