← previous blocknext block →recent activity

Analyzing

Block #73,389,068

11 transactions · 10 stateful · 2026-05-09 04:53:05 UTC

Parallelism

73/100

Blocked

20%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,389,068  ·  11 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

0x22e295f5…1bef

0x065c9d…c394

6 touches
3 conflicts

0xa4b97ef4…5d52

0x065c9d…c394

3 touches
1 conflict

0x18aed20c…48f3

0x000000…012a

2 touches
0 conflicts

0xeda2edc3…91d8

0x000000…012a

2 touches
0 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

2 touches
0 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

2 touches
0 conflicts

0x33018431…8f5c

0x188d58…ea8e

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