Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2abd74dbedb4e2a1b01a46c98792fd4c6ccb32748b99ec449d5d7480ae36227e

Tx prefix hash: dba5febdd8fb255dfac6f9f8b9354b0d42c539c43aab3b06ac5379b3ca2cfffd
Tx public key: f639e8071b1ee0ff3374450999699c92a706f946de14076a0dcc2ec19d3d2689
Timestamp: 1720477945 Timestamp [UCT]: 2024-07-08 22:32:25 Age [y:d:h:m:s]: 00:228:04:58:57
Block: 1061524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162983 RingCT/type: yes/0
Extra: 01f639e8071b1ee0ff3374450999699c92a706f946de14076a0dcc2ec19d3d268902110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f00cc3fd3115b39425222122e1e2db1b49e8c86fda53b3a888a2e03733f2925 0.600000000000 1532015 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": 1061534, "vin": [ { "gen": { "height": 1061524 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f00cc3fd3115b39425222122e1e2db1b49e8c86fda53b3a888a2e03733f2925" } } ], "extra": [ 1, 246, 57, 232, 7, 27, 30, 224, 255, 51, 116, 69, 9, 153, 105, 156, 146, 167, 6, 249, 70, 222, 20, 7, 106, 13, 204, 46, 193, 157, 61, 38, 137, 2, 17, 0, 0, 0, 6, 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