Block #73,597,620

← previous blocknext block →recent activity

Analyzing

Block #73,597,620

10 transactions · 8 stateful · 2026-05-10 04:00:07 UTC

Parallelism

80/100

Blocked

13%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,597,620  ·  10 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x8a35acfb…d1aa

0x8d66a4…3095

4 touches
1 conflict

0x5ba51e87…44ee

0x8d66a4…3095

4 touches
1 conflict

0x664bf99e…0a8c

0x34b655…2a6f

2 touches
0 conflicts

0xac808a27…82db

0x34b655…2a6f

2 touches
0 conflicts

0xbfca3cd0…5023

0x34b655…2a6f

2 touches
0 conflicts

0xd49762c9…1359

0x34b655…2a6f

2 touches
0 conflicts

0x7f430e47…4cbd

0x8d66a4…3095

2 touches
0 conflicts

0x8a35acfb…d1a5

0x8d66a4…3095

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: 0x8d66a43f…113095

1 conflict on slot 0x8a35acfbc1…6bd1aa

← previous block·next block →recent activity