Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: b77f054877347fe26bbd7f2a7d02060f45a006be36c90ad268fe3bcaa1d7daa1

Tx prefix hash: 5a6f45d1d54c097a775f24eaca9c276675a1aa9f4ac51e9929a8bbd4b912182c
Tx public key: bf1e3aa580d96e72234948217d8db49e913fccff2ee15cf55be333f3e019fb14
Timestamp: 1738394856 Timestamp [UTC]: 2025-02-01 07:27:36 Age [y:d:h:m:s]: 01:287:17:40:29
Block: 1209626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 469663 RingCT/type: yes/0
Extra: 01bf1e3aa580d96e72234948217d8db49e913fccff2ee15cf55be333f3e019fb14021100000005007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0cf13c84e2288f137fd937b59917e0e49d7d34593da4cf37f476851466194819 0.000600000000 1696371 of 15 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1209636, "vin": [ { "gen": { "height": 1209626 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cf13c84e2288f137fd937b59917e0e49d7d34593da4cf37f476851466194819" } } ], "extra": [ 1, 191, 30, 58, 165, 128, 217, 110, 114, 35, 73, 72, 33, 125, 141, 180, 158, 145, 63, 204, 255, 46, 225, 92, 245, 91, 227, 51, 243, 224, 25, 251, 20, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: