← previous blocknext block →recent activity

Analyzing

Block #73,499,952

21 transactions · 19 stateful · 2026-05-09 17:11:04 UTC

Parallelism

67/100

Blocked

63%

Avg conflicts / tx

1.43

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,499,952  ·  21 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

0x00000000…0002

0xab3526…fa38

14 touches
21 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x03924cd3…f268

0x8d66a4…3095

5 touches
3 conflicts

0x8a35acfb…d1a9

0x8d66a4…3095

5 touches
3 conflicts

0x00000000…0028

0x1b6862…e19c

4 touches
1 conflict

0x1da7723c…80a7

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0xae69c125…2379

0x2a68ba…90c5

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: 0xab35264b…1cfa38

21 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity