← previous blocknext block →recent activity

Analyzing

Block #73,035,133

29 transactions · 22 stateful · 2026-05-07 13:38:21 UTC

Parallelism

79/100

Blocked

45%

Avg conflicts / tx

0.72

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,035,133  ·  29 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x15b8c035…37a4

0xd32edf…ff58

11 touches
15 conflicts

0xdaca243a…f9de

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0xd574ca…7ab1

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xb8bd6b97…08a2

0x754704…b603

4 touches
1 conflict

0x8a35acfb…d1ac

0x8d66a4…3095

4 touches
1 conflict

0xe89e1a22…ce49

0x8d66a4…3095

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

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

15 conflicts on slot 0x15b8c0354d…f237a4

← previous block·next block →recent activity