← previous blocknext block →recent activity

Analyzing

Block #73,270,574

29 transactions · 21 stateful · 2026-05-08 15:44:47 UTC

Parallelism

86/100

Blocked

43%

Avg conflicts / tx

0.45

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,270,574  ·  29 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xa94cf3f4…554c

0x8d66a4…3095

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xdbc578df…706a

0x34b655…2a6f

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x8a35acfb…d1ae

0x8d66a4…3095

6 touches
3 conflicts

0x00000000…002c

0x1b6862…e19c

4 touches
1 conflict

0xba5743c7…21c3

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

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

3 conflicts on slot 0xa94cf3f4f8…4d554c

← previous block·next block →recent activity