← previous blocknext block →recent activity

Analyzing

Block #73,653,914

35 transactions · 19 stateful · 2026-05-10 10:17:32 UTC

Parallelism

77/100

Blocked

53%

Avg conflicts / tx

0.91

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,653,914  ·  35 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xadc5ab63…ed9c

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0x8d47c9a4…f11d

0x1b6862…e19c

10 touches
10 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x4dd1db39…a996

0x188d58…ea8e

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002b

0x1b6862…e19c

4 touches
1 conflict

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 0xadc5ab635d…aced9c

← previous block·next block →recent activity