Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 411c67ae3c81d54c6735ddfc3a02bc789556071d80bc639ebda34d63e6f7a7f7

Tx prefix hash: 44157d81751c00b60f9309a4aebec456964f03faea20fd8d7966eaccf944bc9a
Tx public key: f494400fcfced7a257781b40ec0dc7f30b7d33b3aac21e9d8e40c948fe01539b
Timestamp: 1732654855 Timestamp [UCT]: 2024-11-26 21:00:55 Age [y:d:h:m:s]: 00:150:14:45:22
Block: 1162374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107475 RingCT/type: yes/0
Extra: 01f494400fcfced7a257781b40ec0dc7f30b7d33b3aac21e9d8e40c948fe01539b0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21be8ce8fa0109fae220335567f622b67dd8bbba4e1fa19d5ed0ae5902add6d5 0.600000000000 1648029 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": 1162384, "vin": [ { "gen": { "height": 1162374 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21be8ce8fa0109fae220335567f622b67dd8bbba4e1fa19d5ed0ae5902add6d5" } } ], "extra": [ 1, 244, 148, 64, 15, 207, 206, 215, 162, 87, 120, 27, 64, 236, 13, 199, 243, 11, 125, 51, 179, 170, 194, 30, 157, 142, 64, 201, 72, 254, 1, 83, 155, 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