← previous blocknext block →recent activity

Analyzing

Block #73,652,263

13 transactions · 10 stateful · 2026-05-10 10:06:22 UTC

Parallelism

77/100

Blocked

30%

Avg conflicts / tx

0.23

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,652,263  ·  13 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x38524fae…9deb

0x34b655…2a6f

4 touches
1 conflict

0x288624c3…6e7f

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x2877f440…c2c8

0x34b655…2a6f

4 touches
1 conflict

0x5ff86a66…51e8

0x065c9d…c394

3 touches
1 conflict

0xbd65fbde…0127

0x065c9d…c394

3 touches
1 conflict

0xf6546231…54ff

0x065c9d…c394

2 touches
0 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

2 touches
0 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

1 conflict on slot 0x38524faed4…ae9deb

← previous block·next block →recent activity