← previous blocknext block →recent activity

Analyzing

Block #73,396,443

9 transactions · 7 stateful · 2026-05-09 05:42:12 UTC

Parallelism

67/100

Blocked

29%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,396,443  ·  9 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

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x92339d95…0800

0x0000a8…8888

2 touches
0 conflicts

0x1059dfd9…9fec

0x065c9d…c394

2 touches
0 conflicts

0x22e295f5…1bef

0x065c9d…c394

2 touches
0 conflicts

0xa83a4bdd…919c

0x065c9d…c394

2 touches
0 conflicts

0xac65c074…7bdb

0x065c9d…c394

2 touches
0 conflicts

0xbf209b31…7e26

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