← previous blocknext block →recent activity

Analyzing

Block #73,795,814

14 transactions · 13 stateful · 2026-05-11 02:15:02 UTC

Parallelism

64/100

Blocked

46%

Avg conflicts / tx

0.93

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,795,814  ·  14 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

0x4aa62980…b3ff

0xd32edf…ff58

9 touches
10 conflicts

0x6aa624fd…a851

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0xdd70bea3…1ffe

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002e

0x1b6862…e19c

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 0x4aa62980dc…cbb3ff

← previous block·next block →recent activity