← previous blocknext block →recent activity

Analyzing

Block #73,513,629

15 transactions · 11 stateful · 2026-05-09 18:42:05 UTC

Parallelism

87/100

Blocked

27%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,513,629  ·  15 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

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x5aebb1e6…5743

0x065c9d…c394

4 touches
1 conflict

0xda6c31ec…ab5b

0x065c9d…c394

4 touches
1 conflict

0xb4bd0113…cf96

0x065c9d…c394

3 touches
1 conflict

0x15b6c022…7f6a

0x065c9d…c394

3 touches
1 conflict

0x22e295f5…1bef

0x065c9d…c394

2 touches
0 conflicts

0x4bfdd5fb…d52b

0x065c9d…c394

2 touches
0 conflicts

0x4d87512b…897c

0x065c9d…c394

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: 0x681e908b…e1ae09

1 conflict on slot 0x0d622e34f9…000000

← previous block·next block →recent activity