Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47703b9150e0f3bbc2b164ee6f1586ef6ec575eaca56dd9a216fe3d83ba2e835

Tx prefix hash: fe4850690dcc824a349794a9331fa8786227ae8aa8f9cce3ceb1563a36d20a5d
Tx public key: 7e1593de6b0b1c5b2bd075c816088419298045ad7e6fd2270bb611dcd6650f30
Timestamp: 1706032949 Timestamp [UCT]: 2024-01-23 18:02:29 Age [y:d:h:m:s]: 01:143:18:37:19
Block: 941731 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363803 RingCT/type: yes/0
Extra: 017e1593de6b0b1c5b2bd075c816088419298045ad7e6fd2270bb611dcd6650f3002110000000379bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b62436668cf47fbc9b6800b42e3f54b1c84dfdd776c68486fc9a83a325e3cff0 0.600000000000 1399887 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": 941741, "vin": [ { "gen": { "height": 941731 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b62436668cf47fbc9b6800b42e3f54b1c84dfdd776c68486fc9a83a325e3cff0" } } ], "extra": [ 1, 126, 21, 147, 222, 107, 11, 28, 91, 43, 208, 117, 200, 22, 8, 132, 25, 41, 128, 69, 173, 126, 111, 210, 39, 11, 182, 17, 220, 214, 101, 15, 48, 2, 17, 0, 0, 0, 3, 121, 189, 163, 190, 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