Block #73,333,803

← previous blocknext block →recent activity

Analyzing

Block #73,333,803

12 transactions · 10 stateful · 2026-05-08 22:45:31 UTC

Parallelism

50/100

Blocked

50%

Avg conflicts / tx

1.08

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,333,803  ·  12 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

0xf853eb8e…4027

0x34b655…2a6f

10 touches
10 conflicts

0xa91c899f…6ee3

0x34b655…2a6f

8 touches
6 conflicts

0x7cbd466f…1700

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xac8e97a0…8426

0x34b655…2a6f

6 touches
3 conflicts

0x2fe4467b…dd70

0x34b655…2a6f

6 touches
3 conflicts

0x55b6a001…1e7a

0x34b655…2a6f

6 touches
3 conflicts

0xaa0d0542…d8ec

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

10 conflicts on slot 0xf853eb8e72…d84027

← previous block·next block →recent activity