← previous blocknext block →recent activity

Analyzing

Block #73,695,080

23 transactions · 18 stateful · 2026-05-10 14:55:16 UTC

Parallelism

48/100

Blocked

67%

Avg conflicts / tx

2.13

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #73,695,080  ·  23 txs across 12 waves  ·  depth 12
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

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

0x5f43e207…da38

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0x529acb6a…fcc6

0x065c9d…c394

10 touches
10 conflicts

0x0ac31945…2c72

0x065c9d…c394

8 touches
6 conflicts

0x00000000…002c

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001c

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 0x5f43e20763…93da38

← previous block·next block →recent activity