Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 119e52a4d5faf6cadca818085f849483d5065260f500a31b0910718f12b42f65

Tx prefix hash: 96ae95a90d8a844e455805bca3cef10aa95ffd5b0c26b08296d3c38cd7d09935
Tx public key: eb6516263b9cbba4c5ce3dfb9651524f1fe5001177a71ff663c7c5675cf8f737
Timestamp: 1723456277 Timestamp [UCT]: 2024-08-12 09:51:17 Age [y:d:h:m:s]: 01:088:20:51:26
Block: 1086208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321984 RingCT/type: yes/0
Extra: 01eb6516263b9cbba4c5ce3dfb9651524f1fe5001177a71ff663c7c5675cf8f73702110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c76fab4c38d530cf007e8f6caa8c64a5c2eec1e7ecbf955b8f80070ce14aae3 0.600000000000 1560803 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": 1086218, "vin": [ { "gen": { "height": 1086208 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c76fab4c38d530cf007e8f6caa8c64a5c2eec1e7ecbf955b8f80070ce14aae3" } } ], "extra": [ 1, 235, 101, 22, 38, 59, 156, 187, 164, 197, 206, 61, 251, 150, 81, 82, 79, 31, 229, 0, 17, 119, 167, 31, 246, 99, 199, 197, 103, 92, 248, 247, 55, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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