Block #73,035,033

← previous blocknext block →recent activity

Analyzing

Block #73,035,033

23 transactions · 18 stateful · 2026-05-07 13:37:42 UTC

Parallelism

83/100

Blocked

33%

Avg conflicts / tx

0.39

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,035,033  ·  23 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

0xc3aacf13…6b3d

0x34b655…2a6f

8 touches
6 conflicts

0x220f4f84…15f8

0x34b655…2a6f

6 touches
3 conflicts

0x8a85cf3d…2868

0x34b655…2a6f

6 touches
3 conflicts

0xf853eb8e…4027

0x34b655…2a6f

6 touches
3 conflicts

0x388e001a…7e04

0x34b655…2a6f

6 touches
3 conflicts

0x5dc14a96…6816

0x34b655…2a6f

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x1b9e654e…0a08

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

6 conflicts on slot 0xc3aacf13f1…5d6b3d

← previous block·next block →recent activity