← previous blocknext block →recent activity

Analyzing

Block #73,493,066

18 transactions · 15 stateful · 2026-05-09 16:25:15 UTC

Parallelism

72/100

Blocked

27%

Avg conflicts / tx

0.44

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,493,066  ·  18 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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…d1ac

0x8d66a4…3095

6 touches
3 conflicts

0x23b2399c…6e4b

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x18b11fba…c92a

0x34b655…2a6f

4 touches
1 conflict

0x28cf9680…8550

0x34b655…2a6f

4 touches
1 conflict

0x2905340c…dbc6

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

3 conflicts on slot 0x8a35acfbc1…6bd1ac

← previous block·next block →recent activity