← previous blocknext block →recent activity

Analyzing

Block #73,795,879

10 transactions · 7 stateful · 2026-05-11 02:15:28 UTC

Parallelism

80/100

Blocked

14%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,795,879  ·  10 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

0x529acb6a…fcc6

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x5b256de9…547f

0x065c9d…c394

2 touches
0 conflicts

0x806205c0…6ab2

0x065c9d…c394

2 touches
0 conflicts

0xce1fe13c…4917

0x065c9d…c394

2 touches
0 conflicts

0xee2e48fa…c427

0x09475a…400f

2 touches
0 conflicts

0x250efed1…5a09

0x607560…d0f5

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

1 conflict on slot 0x529acb6ad1…f0fcc6

← previous block·next block →recent activity