Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9a3803910f954f03f8c13423e1a77c0bc742297cf619c7859c9ac4cc6df6836

Tx prefix hash: ee5a3ea6dd2dfadb7228153fd25bcf1206a76952564efeac30e748330fe12f01
Tx public key: ee2a412e8db7968a078008d20c96d2eae3baedcf8ed068db8e305e0822f84e5d
Timestamp: 1730955819 Timestamp [UCT]: 2024-11-07 05:03:39 Age [y:d:h:m:s]: 00:149:20:25:45
Block: 1148295 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106924 RingCT/type: yes/0
Extra: 01ee2a412e8db7968a078008d20c96d2eae3baedcf8ed068db8e305e0822f84e5d0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7449f0a6508e149db5d827ff6e900142489f4535cd31e356d0aece24992d772d 0.600000000000 1633104 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 dinasty-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": 1148305, "vin": [ { "gen": { "height": 1148295 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7449f0a6508e149db5d827ff6e900142489f4535cd31e356d0aece24992d772d" } } ], "extra": [ 1, 238, 42, 65, 46, 141, 183, 150, 138, 7, 128, 8, 210, 12, 150, 210, 234, 227, 186, 237, 207, 142, 208, 104, 219, 142, 48, 94, 8, 34, 248, 78, 93, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8