Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 449bbc735dc2ad865254c841e6bd139e1a9080e4a04e4e6b6cefcf562826dde7

Tx prefix hash: f7c2707340d8a9b33eb82e63994f8976fd424bb0c9d1cc20ab2dbf85fe268b94
Tx public key: 0aa07019b8a2a0fc11f710f78dab41dab290c67159a5cf34e48e62c648caef5a
Timestamp: 1732730656 Timestamp [UCT]: 2024-11-27 18:04:16 Age [y:d:h:m:s]: 00:141:14:08:02
Block: 1163004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101009 RingCT/type: yes/0
Extra: 010aa07019b8a2a0fc11f710f78dab41dab290c67159a5cf34e48e62c648caef5a0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4aec4e99931e5e9fbb10f9ff8724cd29c47f22cd4060e892165d714b6e419c87 0.600000000000 1648667 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": 1163014, "vin": [ { "gen": { "height": 1163004 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4aec4e99931e5e9fbb10f9ff8724cd29c47f22cd4060e892165d714b6e419c87" } } ], "extra": [ 1, 10, 160, 112, 25, 184, 162, 160, 252, 17, 247, 16, 247, 141, 171, 65, 218, 178, 144, 198, 113, 89, 165, 207, 52, 228, 142, 98, 198, 72, 202, 239, 90, 2, 17, 0, 0, 0, 3, 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