← previous blocknext block →recent activity

Analyzing

Block #73,033,911

19 transactions · 16 stateful · 2026-05-07 13:30:14 UTC

Parallelism

79/100

Blocked

38%

Avg conflicts / tx

0.37

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,033,911  ·  19 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0xd574ca…7ab1

4 touches
1 conflict

0x388e001a…7e04

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0xeaf157e3…bd1a

0xd32edf…ff58

3 touches
1 conflict

0x00000000…001f

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…002f

0x1b6862…e19c

2 touches
0 conflicts

0xba5743c7…21c6

0x1b6862…e19c

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: 0x34b6552d…112a6f

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity