← previous blocknext block →recent activity

Analyzing

Block #73,647,621

36 transactions · 28 stateful · 2026-05-10 09:35:09 UTC

Parallelism

78/100

Blocked

57%

Avg conflicts / tx

0.92

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,647,621  ·  36 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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x8a2657f5…e008

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1ab

0x8d66a4…3095

6 touches
3 conflicts

0xfff38d9f…7063

0x8d66a4…3095

6 touches
3 conflicts

0xde1a0ee7…c75b

0x34b655…2a6f

6 touches
3 conflicts

0xa142fcce…5863

0x34b655…2a6f

6 touches
3 conflicts

0xea5be56d…cba0

0x34b655…2a6f

6 touches
3 conflicts

0x8be69bbb…7afe

0xd32edf…ff58

5 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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity