← previous blocknext block →recent activity

Analyzing

Block #73,679,567

33 transactions · 22 stateful · 2026-05-10 13:10:44 UTC

Parallelism

85/100

Blocked

32%

Avg conflicts / tx

0.48

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,679,567  ·  33 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x05d869f4…64a5

0xd32edf…ff58

9 touches
10 conflicts

0xf2438038…5fa7

0x34b655…2a6f

6 touches
3 conflicts

0x2b9c6652…d14e

0x754704…b603

4 touches
1 conflict

0x00f7e3b7…e015

0x188d58…ea8e

4 touches
1 conflict

0xdd70bea3…1ffe

0x3bd359…433a

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00f7e3b7…e017

0x188d58…ea8e

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

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

10 conflicts on slot 0x05d869f4a2…f964a5

← previous block·next block →recent activity