← previous blocknext block →recent activity

Analyzing

Block #73,795,898

27 transactions · 21 stateful · 2026-05-11 02:15:36 UTC

Parallelism

85/100

Blocked

38%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,795,898  ·  27 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

0x0e6affbd…91da

0xd32edf…ff58

7 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0004

0x9b60e5…f8ac

4 touches
1 conflict

0xee0a9ebb…c425

0x0555e3…2b9c

4 touches
1 conflict

0x3e733ae4…4598

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0xb409e204…89ac

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…641c

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

6 conflicts on slot 0x0e6affbd3c…1291da

← previous block·next block →recent activity