← previous blocknext block →recent activity

Analyzing

Block #73,963,439

11 transactions · 11 stateful · 2026-05-11 20:51:52 UTC

Parallelism

73/100

Blocked

27%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,963,439  ·  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

0xf537eaa0…73c8

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xa472d565…9fe4

0x3bd359…433a

4 touches
1 conflict

0xbf25e763…684f

0x3bd359…433a

4 touches
1 conflict

0x00000000…0000

0x776059…1d8d

4 touches
1 conflict

0x00000000…0001

0x776059…1d8d

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x44ad89ba…cf83

0xde22b2…7777

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: 0x065c9d28…a9c394

3 conflicts on slot 0xf537eaa0c6…3873c8

← previous block·next block →recent activity