← previous blocknext block →recent activity

Analyzing

Block #73,795,811

26 transactions · 19 stateful · 2026-05-11 02:15:00 UTC

Parallelism

77/100

Blocked

47%

Avg conflicts / tx

0.92

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,795,811  ·  26 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0x8a35acfb…d1ae

0x8d66a4…3095

8 touches
6 conflicts

0x3e733ae4…4598

0x34b655…2a6f

6 touches
3 conflicts

0x57de3828…3fbb

0x34b655…2a6f

6 touches
3 conflicts

0x5d70606a…1d53

0x34b655…2a6f

6 touches
3 conflicts

0x5de96bd3…c60c

0x34b655…2a6f

6 touches
3 conflicts

0xa009aa7b…a5ba

0x34b655…2a6f

6 touches
3 conflicts

0xa80253b7…135e

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: 0x34b6552d…112a6f

15 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity