← previous blocknext block →recent activity

Analyzing

Block #73,753,180

35 transactions · 29 stateful · 2026-05-10 21:27:22 UTC

Parallelism

63/100

Blocked

66%

Avg conflicts / tx

2.46

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #73,753,180  ·  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

0x0add5973…0926

0xd32edf…ff58

23 touches
66 conflicts

0x00000000…0001

0x116e7d…d8f1

10 touches
10 conflicts

0x00000000…0003

0x116e7d…d8f1

10 touches
10 conflicts

0x00000000…0000

0x116e7d…d8f1

10 touches
10 conflicts

0x692a4122…76b8

0x350035…7777

10 touches
10 conflicts

0xb7143610…adc4

0x3bd359…433a

10 touches
10 conflicts

0x5de96bd3…c60c

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

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

66 conflicts on slot 0x0add5973e3…2e0926

← previous block·next block →recent activity