← previous blocknext block →recent activity

Analyzing

Block #73,811,521

21 transactions · 17 stateful · 2026-05-11 04:00:18 UTC

Parallelism

52/100

Blocked

65%

Avg conflicts / tx

2.29

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #73,811,521  ·  21 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

0xcffdf115…37f2

0xd32edf…ff58

19 touches
45 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001f

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002f

0x1b6862…e19c

4 touches
1 conflict

0x792299c4…16b8

0x1b6862…e19c

4 touches
1 conflict

0xa91c899f…6ee3

0x34b655…2a6f

4 touches
1 conflict

0xaa0d0542…d8ec

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 0xcffdf11567…7e37f2

← previous block·next block →recent activity