← previous blocknext block →recent activity

Analyzing

Block #73,046,267

26 transactions · 22 stateful · 2026-05-07 14:52:29 UTC

Parallelism

62/100

Blocked

50%

Avg conflicts / tx

1.81

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #73,046,267  ·  26 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x2f096f4f…510c

0xd32edf…ff58

19 touches
45 conflicts

0x00857068…2bc4

0x065c9d…c394

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002f

0x1b6862…e19c

4 touches
1 conflict

0xba5743c7…21c6

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x70b2f813…783c

0x2a68ba…90c5

4 touches
1 conflict

0xea02471d…1539

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: 0xd32edf66…9fff58

45 conflicts on slot 0x2f096f4f5c…e4510c

← previous block·next block →recent activity