Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20d4af758f0d39eeaac18d7240b032494e806ea5b8a959c2c09089f932ab5969

Tx prefix hash: 09ee64da0069f9e505626999d9912fff40802e3bc5c815ae04f19a26800691a1
Tx public key: e4c24888b52fbf7ace08c93de2756fe3b23cf87ad5724b8dd382ceb0fffdbd60
Timestamp: 1732583770 Timestamp [UCT]: 2024-11-26 01:16:10 Age [y:d:h:m:s]: 00:204:06:05:18
Block: 1161780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145717 RingCT/type: yes/0
Extra: 01e4c24888b52fbf7ace08c93de2756fe3b23cf87ad5724b8dd382ceb0fffdbd600211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e35fdaf580e19ca92f23007629aec4c3b52f92b88acc1d9c61851cb821b98bd 0.600000000000 1647435 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": 1161790, "vin": [ { "gen": { "height": 1161780 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e35fdaf580e19ca92f23007629aec4c3b52f92b88acc1d9c61851cb821b98bd" } } ], "extra": [ 1, 228, 194, 72, 136, 181, 47, 191, 122, 206, 8, 201, 61, 226, 117, 111, 227, 178, 60, 248, 122, 213, 114, 75, 141, 211, 130, 206, 176, 255, 253, 189, 96, 2, 17, 0, 0, 0, 4, 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