← previous blocknext block →recent activity

Analyzing

Block #73,041,790

35 transactions · 27 stateful · 2026-05-07 14:22:38 UTC

Parallelism

63/100

Blocked

63%

Avg conflicts / tx

2.4

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #73,041,790  ·  35 txs across 13 waves  ·  depth 13
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

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

0x60909886…f03c

0xd32edf…ff58

25 touches
78 conflicts

0x00000000…0013

0x1b6862…e19c

16 touches
28 conflicts

0x00000000…0015

0x1b6862…e19c

16 touches
28 conflicts

0x00000000…001f

0x1b6862…e19c

16 touches
28 conflicts

0x00000000…002f

0x1b6862…e19c

16 touches
28 conflicts

0x73912233…4589

0x1b6862…e19c

16 touches
28 conflicts

0x00000000…0012

0x1b6862…e19c

16 touches
28 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

16 touches
28 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

78 conflicts on slot 0x6090988683…0df03c

← previous block·next block →recent activity