← previous blocknext block →recent activity

Analyzing

Block #73,651,705

28 transactions · 23 stateful · 2026-05-10 10:02:37 UTC

Parallelism

79/100

Blocked

57%

Avg conflicts / tx

0.86

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,651,705  ·  28 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x0e75b9a4…e3c1

0xd32edf…ff58

9 touches
10 conflicts

0xc875b8db…299f

0x34b655…2a6f

8 touches
6 conflicts

0xf2438038…5fa7

0x34b655…2a6f

8 touches
6 conflicts

0x5618dbe3…ca7b

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0000

0x63e48b…53f2

6 touches
3 conflicts

0x00000000…0002

0x63e48b…53f2

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 0x0e75b9a4c8…64e3c1

← previous block·next block →recent activity