Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ae94fb746c1e236ad78130baede6deaca59eb610957258de4093d34ddfc9087

Tx prefix hash: 72c622fc9c62efc8e3a27cec8b93b1ce6f013617a6d6f7d0a4c594e243423b8e
Tx public key: 72de2254cb0491074f2cd4761915816f8b801c90a74764056e7cdf0aa5ed0186
Timestamp: 1735092196 Timestamp [UCT]: 2024-12-25 02:03:16 Age [y:d:h:m:s]: 00:089:01:11:18
Block: 1182569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63405 RingCT/type: yes/0
Extra: 0172de2254cb0491074f2cd4761915816f8b801c90a74764056e7cdf0aa5ed01860211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe9b535a84629aa0e6e060179b00c57e6844ac043b2f9088e6294dc4649cdd5d 0.600000000000 1669004 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": 1182579, "vin": [ { "gen": { "height": 1182569 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe9b535a84629aa0e6e060179b00c57e6844ac043b2f9088e6294dc4649cdd5d" } } ], "extra": [ 1, 114, 222, 34, 84, 203, 4, 145, 7, 79, 44, 212, 118, 25, 21, 129, 111, 139, 128, 28, 144, 167, 71, 100, 5, 110, 124, 223, 10, 165, 237, 1, 134, 2, 17, 0, 0, 0, 1, 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