Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f40347c7fcc2ca17f8f978005c8f09f027a6beef37396abb3c8e56a1d1d1cfc

Tx prefix hash: dabfc854e4782a8a70ca9f0d1a2cbb60bd4b506190e5b29724fe16dddfa9053b
Tx public key: 32120acddea44ddc5ec5e020700c24678f5b58ad6bb86887af3a9dca9599e12a
Timestamp: 1709001895 Timestamp [UCT]: 2024-02-27 02:44:55 Age [y:d:h:m:s]: 01:081:20:40:37
Block: 966382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319537 RingCT/type: yes/0
Extra: 0132120acddea44ddc5ec5e020700c24678f5b58ad6bb86887af3a9dca9599e12a0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52b664cd4e7c2af4d3ff70176d263a7d5f8929aef1ebc4f476edb2d07e523444 0.600000000000 1426139 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": 966392, "vin": [ { "gen": { "height": 966382 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52b664cd4e7c2af4d3ff70176d263a7d5f8929aef1ebc4f476edb2d07e523444" } } ], "extra": [ 1, 50, 18, 10, 205, 222, 164, 77, 220, 94, 197, 224, 32, 112, 12, 36, 103, 143, 91, 88, 173, 107, 184, 104, 135, 175, 58, 157, 202, 149, 153, 225, 42, 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