← previous blocknext block →recent activity

Analyzing

Block #73,680,904

16 transactions · 8 stateful · 2026-05-10 13:19:46 UTC

Parallelism

88/100

Blocked

13%

Avg conflicts / tx

0.06

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,680,904  ·  16 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

0x00bac013…a28c

0xfd44b3…00d1

4 touches
1 conflict

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x265f1e90…2a84

0x065c9d…c394

2 touches
0 conflicts

0x3f80a230…c48e

0x065c9d…c394

2 touches
0 conflicts

0x437a9023…c88c

0x065c9d…c394

2 touches
0 conflicts

0x529acb6a…fcc6

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: 0xfd44b351…7f00d1

1 conflict on slot 0x00bac0131a…bba28c

← previous block·next block →recent activity