← previous blocknext block →recent activity

Analyzing

Block #73,748,856

39 transactions · 29 stateful · 2026-05-10 20:58:11 UTC

Parallelism

85/100

Blocked

59%

Avg conflicts / tx

1.1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,748,856  ·  39 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

0x4017ed8a…7db5

0xd32edf…ff58

11 touches
15 conflicts

0x15d039e7…4bb6

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x9753c6ec…6479

0x34b655…2a6f

8 touches
6 conflicts

0x057de4f5…df60

0x34b655…2a6f

8 touches
6 conflicts

0xa91c899f…6ee3

0x34b655…2a6f

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1ad

0x8d66a4…3095

8 touches
6 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

15 conflicts on slot 0x4017ed8a4b…797db5

← previous block·next block →recent activity