Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f44c921fd995deed9e055517184be4ea298f2c942c760c91ddcb816040241c86

Tx prefix hash: aaf3d55e1ab8114384422bcd132833bcf18edc2a841ae438d5e0e1fec781dcd0
Tx public key: fc1079e7da7c527e047950a535f9b306664f252c7727f2d2cafaf59c62434090
Timestamp: 1736459233 Timestamp [UCT]: 2025-01-09 21:47:13 Age [y:d:h:m:s]: 00:160:20:09:15
Block: 1193874 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114648 RingCT/type: yes/0
Extra: 01fc1079e7da7c527e047950a535f9b306664f252c7727f2d2cafaf59c624340900211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ae5c585ccc6b64ce22df3994de16aa30f4cdd98ab7eca7faeddb652803bff7a 0.600000000000 1680439 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": 1193884, "vin": [ { "gen": { "height": 1193874 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ae5c585ccc6b64ce22df3994de16aa30f4cdd98ab7eca7faeddb652803bff7a" } } ], "extra": [ 1, 252, 16, 121, 231, 218, 124, 82, 126, 4, 121, 80, 165, 53, 249, 179, 6, 102, 79, 37, 44, 119, 39, 242, 210, 202, 250, 245, 156, 98, 67, 64, 144, 2, 17, 0, 0, 0, 6, 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