Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb695498303f18b2cc70652a2f850c6e671a121e4ea5653f7acbcce72e4de0ec

Tx prefix hash: 397bf6de0bd6f93f82f1b308878355a22e5875c165a1fd9e9493faa120c7daae
Tx public key: 16b78adffc36e1e08074f2e58dcf84a4f2027f9938116062f27dcff5acb03207
Timestamp: 1732929689 Timestamp [UCT]: 2024-11-30 01:21:29 Age [y:d:h:m:s]: 00:118:00:17:42
Block: 1164650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84142 RingCT/type: yes/0
Extra: 0116b78adffc36e1e08074f2e58dcf84a4f2027f9938116062f27dcff5acb03207021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0c561e165cd8fa8c27ea5be84edcfb4ccc5f0ea9ab5566dac79d71f2da04d45 0.600000000000 1650323 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": 1164660, "vin": [ { "gen": { "height": 1164650 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0c561e165cd8fa8c27ea5be84edcfb4ccc5f0ea9ab5566dac79d71f2da04d45" } } ], "extra": [ 1, 22, 183, 138, 223, 252, 54, 225, 224, 128, 116, 242, 229, 141, 207, 132, 164, 242, 2, 127, 153, 56, 17, 96, 98, 242, 125, 207, 245, 172, 176, 50, 7, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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