← previous blocknext block →recent activity

Analyzing

Block #73,846,249

12 transactions · 12 stateful · 2026-05-11 07:51:22 UTC

Parallelism

67/100

Blocked

50%

Avg conflicts / tx

0.92

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,846,249  ·  12 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

0xb81d3ee7…3947

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x8240d70c…7c3b

0x34b655…2a6f

6 touches
3 conflicts

0x468c69b1…af11

0x8d66a4…3095

6 touches
3 conflicts

0x8a35acfb…d1ac

0x8d66a4…3095

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001f

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002f

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

6 conflicts on slot 0xb81d3ee780…143947

← previous block·next block →recent activity