← previous blocknext block →recent activity

Analyzing

Block #73,753,181

36 transactions · 20 stateful · 2026-05-10 21:27:22 UTC

Parallelism

69/100

Blocked

75%

Avg conflicts / tx

1.94

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #73,753,181  ·  36 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x25ee5018…c808

0xd32edf…ff58

21 touches
55 conflicts

0xd06cc746…27e4

0x350035…7777

12 touches
15 conflicts

0xfe3bddd2…8b48

0x3bd359…433a

8 touches
6 conflicts

0x692a4122…76b8

0x350035…7777

4 touches
1 conflict

0x00000000…0003

0x116e7d…d8f1

4 touches
1 conflict

0x00000000…0001

0x116e7d…d8f1

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x00000000…0000

0x116e7d…d8f1

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

55 conflicts on slot 0x25ee5018c0…15c808

← previous block·next block →recent activity