← previous blocknext block →recent activity

Analyzing

Block #73,595,446

28 transactions · 20 stateful · 2026-05-10 03:45:41 UTC

Parallelism

68/100

Blocked

65%

Avg conflicts / tx

1.29

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,595,446  ·  28 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0xa91c899f…6ee3

0x34b655…2a6f

10 touches
10 conflicts

0x8a35acfb…d1aa

0x8d66a4…3095

8 touches
6 conflicts

0xd84e22f4…ccfb

0x34b655…2a6f

8 touches
6 conflicts

0x8240d70c…7c3b

0x34b655…2a6f

8 touches
6 conflicts

0xc6417de0…2191

0xc8689a…ee79

6 touches
3 conflicts

0x4ae4b486…d0ec

0x34b655…2a6f

6 touches
3 conflicts

0x6eba5e7f…4b52

0x34b655…2a6f

6 touches
3 conflicts

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

15 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity