Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0303bba571b6e5cd02fb2479a4b0427b0f79becdd8e80e9a466c8dfe9ef7f775

Tx prefix hash: 7ea79d54dc7c341890b30607ab689b06a9979524ae26f12d7019342855a59bce
Tx public key: 352c97d5a947f369f34553de419a9ff5f84948105dc5c870290830ef457d1644
Timestamp: 1582109974 Timestamp [UCT]: 2020-02-19 10:59:34 Age [y:d:h:m:s]: 04:285:21:45:05
Block: 68089 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1096789 RingCT/type: yes/0
Extra: 01352c97d5a947f369f34553de419a9ff5f84948105dc5c870290830ef457d164402110000000e4943cd9f000000000000000000

1 output(s) for total of 365.084743301000 dcy

stealth address amount amount idx
00: b3a73b3d39c0bf9aa9b241d2bccf04e2dbd4bb8720675a01f494da61515c9bea 365.084743301000 125455 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": 68099, "vin": [ { "gen": { "height": 68089 } } ], "vout": [ { "amount": 365084743301, "target": { "key": "b3a73b3d39c0bf9aa9b241d2bccf04e2dbd4bb8720675a01f494da61515c9bea" } } ], "extra": [ 1, 53, 44, 151, 213, 169, 71, 243, 105, 243, 69, 83, 222, 65, 154, 159, 245, 248, 73, 72, 16, 93, 197, 200, 112, 41, 8, 48, 239, 69, 125, 22, 68, 2, 17, 0, 0, 0, 14, 73, 67, 205, 159, 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