Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 560e6ee59988748bcf382a79764db3a72d3a26258772e723fcb4392aad33e04c

Tx prefix hash: fcc2d234d040aaad02b6081a19d5a73421f0741d80165d3d7b49af70700009dc
Tx public key: 1a9a39e5426c5415afbfc645e67ee7a543c30fef0dffe0f896ce6d657b076f68
Timestamp: 1708453482 Timestamp [UCT]: 2024-02-20 18:24:42 Age [y:d:h:m:s]: 01:086:13:43:12
Block: 961826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322929 RingCT/type: yes/0
Extra: 011a9a39e5426c5415afbfc645e67ee7a543c30fef0dffe0f896ce6d657b076f680211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f99e9188a76efd9e9a657a3c311ad1c56aeda45a2633e7f9862b2d4cd9560829 0.600000000000 1421439 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": 961836, "vin": [ { "gen": { "height": 961826 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f99e9188a76efd9e9a657a3c311ad1c56aeda45a2633e7f9862b2d4cd9560829" } } ], "extra": [ 1, 26, 154, 57, 229, 66, 108, 84, 21, 175, 191, 198, 69, 230, 126, 231, 165, 67, 195, 15, 239, 13, 255, 224, 248, 150, 206, 109, 101, 123, 7, 111, 104, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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