Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e3d66217bcf87839f757ec090d0d02ef593e6f0610a5abe29f3ce4fd09736d6

Tx prefix hash: 4b78ad32d988dfe5d65454d161dc1d12ccea454d3e9b663c470c82f74b4c6b5a
Tx public key: 31aeb3cee7109ca54122979aa52fe4a719478403b3a4dbd5519854178f6e0743
Timestamp: 1709100838 Timestamp [UCT]: 2024-02-28 06:13:58 Age [y:d:h:m:s]: 01:036:12:49:46
Block: 967200 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287116 RingCT/type: yes/0
Extra: 0131aeb3cee7109ca54122979aa52fe4a719478403b3a4dbd5519854178f6e07430211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8be5acef769c91bb2a4b4d98db5093b6c4d5d854500c50f3bc795b8e7af304bc 0.600000000000 1426971 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": 967210, "vin": [ { "gen": { "height": 967200 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8be5acef769c91bb2a4b4d98db5093b6c4d5d854500c50f3bc795b8e7af304bc" } } ], "extra": [ 1, 49, 174, 179, 206, 231, 16, 156, 165, 65, 34, 151, 154, 165, 47, 228, 167, 25, 71, 132, 3, 179, 164, 219, 213, 81, 152, 84, 23, 143, 110, 7, 67, 2, 17, 0, 0, 0, 2, 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