← previous blocknext block →recent activity

Analyzing

Block #73,681,644

34 transactions · 23 stateful · 2026-05-10 13:24:45 UTC

Parallelism

74/100

Blocked

48%

Avg conflicts / tx

1.18

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,681,644  ·  34 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

0xd26ba05b…f0f0

0xd32edf…ff58

17 touches
36 conflicts

0x00000000…002c

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

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

0x9ac040c1…8223

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

36 conflicts on slot 0xd26ba05b02…57f0f0

← previous block·next block →recent activity