← previous blocknext block →recent activity

Analyzing

Block #73,661,023

14 transactions · 11 stateful · 2026-05-10 11:05:25 UTC

Parallelism

79/100

Blocked

18%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,661,023  ·  14 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xb159af88…a9e7

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xd2b65c96…86d1

0x065c9d…c394

2 touches
0 conflicts

0x1abf30aa…8287

0x1001ff…1001

2 touches
0 conflicts

0xc6f1b3af…c97c

0x1001ff…1001

2 touches
0 conflicts

0x00000000…0000

0x276664…5732

2 touches
0 conflicts

0x00000000…0002

0x276664…5732

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 0x0000000000…00003d

← previous block·next block →recent activity