← previous blocknext block →recent activity

Analyzing

Block #73,683,180

29 transactions · 22 stateful · 2026-05-10 13:35:08 UTC

Parallelism

76/100

Blocked

45%

Avg conflicts / tx

0.79

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,683,180  ·  29 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

10 touches
10 conflicts

0x529acb6a…fcc6

0x065c9d…c394

10 touches
10 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x8a35acfb…d1ab

0x8d66a4…3095

6 touches
3 conflicts

0x90de7750…0335

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…002c

0x1b6862…e19c

4 touches
1 conflict

0x91220b8f…7a05

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

10 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity