Block #73,493,128

← previous blocknext block →recent activity

Analyzing

Block #73,493,128

15 transactions · 11 stateful · 2026-05-09 16:25:39 UTC

Parallelism

60/100

Blocked

55%

Avg conflicts / tx

0.93

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,493,128  ·  15 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

0xa91c899f…6ee3

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x868859b9…3db5

0x34b655…2a6f

8 touches
6 conflicts

0xf7c5003c…8dc0

0x34b655…2a6f

6 touches
3 conflicts

0x7b50a82b…f53d

0x34b655…2a6f

4 touches
1 conflict

0x7cbd466f…1700

0x34b655…2a6f

4 touches
1 conflict

0x8240d70c…7c3b

0x34b655…2a6f

4 touches
1 conflict

0x8db1e0f2…2fcf

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 0xa91c899f02…fa6ee3

← previous block·next block →recent activity