← previous blocknext block →recent activity

Analyzing

Block #73,869,047

17 transactions · 12 stateful · 2026-05-11 10:23:30 UTC

Parallelism

76/100

Blocked

33%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,869,047  ·  17 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

0x00000000…0007

0x1414f3…5137

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0xfac61869…a55b

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0xc3d335c1…ae85

0xd32edf…ff58

3 touches
1 conflict

0xa0b5fc75…8ee7

0x065c9d…c394

2 touches
0 conflicts

0xb159af88…a9e7

0x065c9d…c394

2 touches
0 conflicts

0xd72be1f4…9f64

0x065c9d…c394

2 touches
0 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: 0x1414f3ba…045137

6 conflicts on slot 0x0000000000…000007

← previous block·next block →recent activity