← previous blocknext block →recent activity

Analyzing

Block #73,956,322

27 transactions · 19 stateful · 2026-05-11 20:04:33 UTC

Parallelism

67/100

Blocked

47%

Avg conflicts / tx

1.11

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,956,322  ·  27 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xd38726a0…46af

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0xd996735f…8730

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001a

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002a

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

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

28 conflicts on slot 0xd38726a01f…0c46af

← previous block·next block →recent activity