Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51e62f5e0ccb260893b3153ae45a20872ac4a2fceb6a44bdfa92a05be4d66fee

Tx prefix hash: 5f7c73658236793869a108d2a127e040d6fd615d0e273eb81d0ea8a01e28e10c
Tx public key: 2de34c5a4228505c536aae25d4ef5096079fe87be7a5f4f99b30c2e6c74f9a1d
Timestamp: 1753152293 Timestamp [UTC]: 2025-07-22 02:44:53 Age [y:d:h:m:s]: 01:119:13:04:11
Block: 1330655 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350566 RingCT/type: yes/0
Extra: 012de34c5a4228505c536aae25d4ef5096079fe87be7a5f4f99b30c2e6c74f9a1d021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7673149034d9d462bc73decd50a08bff70e430fdce2a65cc7383d15e6b73e16c 0.000600000000 1818448 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": 1330665, "vin": [ { "gen": { "height": 1330655 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7673149034d9d462bc73decd50a08bff70e430fdce2a65cc7383d15e6b73e16c" } } ], "extra": [ 1, 45, 227, 76, 90, 66, 40, 80, 92, 83, 106, 174, 37, 212, 239, 80, 150, 7, 159, 232, 123, 231, 165, 244, 249, 155, 48, 194, 230, 199, 79, 154, 29, 2, 17, 0, 0, 0, 2, 191, 81, 178, 162, 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: