← previous blocknext block →recent activity

Analyzing

Block #73,499,575

31 transactions · 22 stateful · 2026-05-09 17:08:33 UTC

Parallelism

87/100

Blocked

41%

Avg conflicts / tx

0.45

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,499,575  ·  31 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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x8240d70c…7c3b

0x34b655…2a6f

6 touches
3 conflicts

0xb81d3ee7…3947

0x34b655…2a6f

6 touches
3 conflicts

0xe429e4c9…9510

0x34b655…2a6f

6 touches
3 conflicts

0x01e7b865…6e6e

0x188d58…ea8e

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x207fb267…de78

0x34b655…2a6f

4 touches
1 conflict

0x664bf99e…0a8c

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity