← previous blocknext block →recent activity

Analyzing

Block #73,809,719

11 transactions · 10 stateful · 2026-05-11 03:48:21 UTC

Parallelism

73/100

Blocked

40%

Avg conflicts / tx

0.64

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,809,719  ·  11 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x8a35acfb…d1ae

0x8d66a4…3095

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x157b6348…8604

0x34b655…2a6f

6 touches
3 conflicts

0x2b088f80…4cf9

0x34b655…2a6f

4 touches
1 conflict

0x2d30fc61…d621

0x34b655…2a6f

4 touches
1 conflict

0x3a55534b…8728

0x34b655…2a6f

4 touches
1 conflict

0x404dbe6c…c67a

0x34b655…2a6f

4 touches
1 conflict

0x664bf99e…0a8c

0x34b655…2a6f

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: 0x8d66a43f…113095

3 conflicts on slot 0x8a35acfbc1…6bd1ae

← previous block·next block →recent activity