Block #73,358,961

← previous blocknext block →recent activity

Analyzing

Block #73,358,961

18 transactions · 15 stateful · 2026-05-09 01:32:48 UTC

Parallelism

67/100

Blocked

33%

Avg conflicts / tx

0.72

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,358,961  ·  18 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

0xac2a0273…721b

0x34b655…2a6f

10 touches
10 conflicts

0xf6c9bf9b…ac02

0x34b655…2a6f

10 touches
10 conflicts

0xc1f730bf…5d8e

0x34b655…2a6f

8 touches
6 conflicts

0x280d1119…ee4d

0x34b655…2a6f

8 touches
6 conflicts

0x664bf99e…0a8c

0x34b655…2a6f

6 touches
3 conflicts

0x7a8ea002…f67f

0x34b655…2a6f

6 touches
3 conflicts

0x7cb2f3fa…4836

0x34b655…2a6f

6 touches
3 conflicts

0x88b2c8b9…6537

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

10 conflicts on slot 0xac2a02739b…81721b

← previous block·next block →recent activity