← previous blocknext block →recent activity

Analyzing

Block #73,504,686

8 transactions · 7 stateful · 2026-05-09 17:42:40 UTC

Parallelism

50/100

Blocked

43%

Avg conflicts / tx

0.75

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,504,686  ·  8 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x48bdea5f…959e

0x065c9d…c394

4 touches
1 conflict

0x3e1cd845…d52a

0x065c9d…c394

4 touches
1 conflict

0x2224dc93…f72b

0x065c9d…c394

3 touches
1 conflict

0x416eef6e…46f9

0x065c9d…c394

3 touches
1 conflict

0xa89a0eab…17ed

0x065c9d…c394

3 touches
1 conflict

0x4d87512b…897c

0x065c9d…c394

2 touches
0 conflicts

0x519fa8f0…b9cf

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity