Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d33ffe2696a798b9c7eaf5ad308cde152860b882fc96d4e8648ce74ff8ab56c

Tx prefix hash: 7ec588c14c8e7007c3e8be9b733712784a5f3df5a221579d201b4a269ff0e601
Tx public key: bae80e52f91e531e189d34543cb2ab0daa17d32335bdec80f827e09ca924dbcc
Timestamp: 1648674924 Timestamp [UTC]: 2022-03-30 21:15:24 Age [y:d:h:m:s]: 04:231:20:22:30
Block: 469835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1209959 RingCT/type: yes/0
Extra: 01bae80e52f91e531e189d34543cb2ab0daa17d32335bdec80f827e09ca924dbcc02110000000237cb3088000000000000000000

1 output(s) for total of 0.017031066979 xmr

stealth address amount amount idx tag
00: b70c086da1d8de5241c1e3ff9f88d649f9924dfe301a7898ab810f8d8e7d9990 0.017031066979 888855 of 0 -

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": 469845, "vin": [ { "gen": { "height": 469835 } } ], "vout": [ { "amount": 17031066979, "target": { "key": "b70c086da1d8de5241c1e3ff9f88d649f9924dfe301a7898ab810f8d8e7d9990" } } ], "extra": [ 1, 186, 232, 14, 82, 249, 30, 83, 30, 24, 157, 52, 84, 60, 178, 171, 13, 170, 23, 211, 35, 53, 189, 236, 128, 248, 39, 224, 156, 169, 36, 219, 204, 2, 17, 0, 0, 0, 2, 55, 203, 48, 136, 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: