Block #73,651,621

← previous blocknext block →recent activity

Analyzing

Block #73,651,621

13 transactions · 13 stateful · 2026-05-10 10:02:04 UTC

Parallelism

77/100

Blocked

23%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,651,621  ·  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

0xbc639dd4…48c7

0xd32edf…ff58

5 touches
3 conflicts

0xf2438038…5fa7

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x529acb6a…fcc6

0x065c9d…c394

4 touches
1 conflict

0xbeb3d52d…df93

0x065c9d…c394

2 touches
0 conflicts

0xde03553a…2510

0x065c9d…c394

2 touches
0 conflicts

0xc9e97522…3519

0x2a68ba…90c5

2 touches
0 conflicts

0x005bcc9d…5141

0x34b655…2a6f

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: 0xd32edf66…9fff58

3 conflicts on slot 0xbc639dd440…3648c7

← previous block·next block →recent activity