Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4caf7ad48e191eb150774a12bb62a1f6115669302fbf6a0f84ebe62cfcb9c10a

Tx prefix hash: 6d53353cd67dbd78a7b477f6ec2f70c857297606dbe47e678f42bd6a677b940a
Tx public key: 167592d3e9bd03cef2e4d88d1239a0f7df9a304c3fca81b0f296edf36fef5749
Timestamp: 1723504834 Timestamp [UCT]: 2024-08-12 23:20:34 Age [y:d:h:m:s]: 00:216:12:55:52
Block: 1086611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154654 RingCT/type: yes/0
Extra: 01167592d3e9bd03cef2e4d88d1239a0f7df9a304c3fca81b0f296edf36fef574902110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9594d47a7daeffb88dd30391c5cbc8cf91547907a70ee73059c0ad8fffbf881 0.600000000000 1561208 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": 1086621, "vin": [ { "gen": { "height": 1086611 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9594d47a7daeffb88dd30391c5cbc8cf91547907a70ee73059c0ad8fffbf881" } } ], "extra": [ 1, 22, 117, 146, 211, 233, 189, 3, 206, 242, 228, 216, 141, 18, 57, 160, 247, 223, 154, 48, 76, 63, 202, 129, 176, 242, 150, 237, 243, 111, 239, 87, 73, 2, 17, 0, 0, 0, 3, 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