Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35c68025e8fb80fac4dca897a9a77d4691818069ec5cfc80ed16d59dc232366e

Tx prefix hash: 3eb4507b4f3e7b5e25d5c78c55044a3b8b3fd6cfcef2250bcf1c3cea3b5324f2
Tx public key: 80c1a00157ae0f67bffeb4e4ecf59e4ecf20a0bc91dd592f074cfd3175631f92
Timestamp: 1577201899 Timestamp [UCT]: 2019-12-24 15:38:19 Age [y:d:h:m:s]: 05:045:10:13:20
Block: 30839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1182198 RingCT/type: yes/0
Extra: 0180c1a00157ae0f67bffeb4e4ecf59e4ecf20a0bc91dd592f074cfd3175631f920211000000044ac5aa02000000000000000000

1 output(s) for total of 485.085677741000 dcy

stealth address amount amount idx
00: d1b9dfaf66b9dcf2dd3b25bcabd1ff2e6ae54c0f4ac9e4a235d739b2c472d3db 485.085677741000 50901 of 0

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": 30849, "vin": [ { "gen": { "height": 30839 } } ], "vout": [ { "amount": 485085677741, "target": { "key": "d1b9dfaf66b9dcf2dd3b25bcabd1ff2e6ae54c0f4ac9e4a235d739b2c472d3db" } } ], "extra": [ 1, 128, 193, 160, 1, 87, 174, 15, 103, 191, 254, 180, 228, 236, 245, 158, 78, 207, 32, 160, 188, 145, 221, 89, 47, 7, 76, 253, 49, 117, 99, 31, 146, 2, 17, 0, 0, 0, 4, 74, 197, 170, 2, 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