← previous blocknext block →recent activity

Analyzing

Block #73,336,268

17 transactions · 11 stateful · 2026-05-08 23:01:51 UTC

Parallelism

71/100

Blocked

36%

Avg conflicts / tx

0.47

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,336,268  ·  17 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x6f08361d…bda6

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x438cf5f6…f077

0x2a68ba…90c5

4 touches
1 conflict

0x38d6e8d7…f609

0xd32edf…ff58

3 touches
1 conflict

0x00000000…000a

0x09f880…ede0

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

2 touches
0 conflicts

0xb5cfe5ac…20b4

0x3bd359…433a

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

6 conflicts on slot 0x6f08361da9…89bda6

← previous block·next block →recent activity