Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf7265d492e70e1b90a3904d9fa7266c66233805e4c9c9db35018e5017a1c927

Tx prefix hash: a561ce98cfb9627889d074ee7b396fee45ea6072665a33340df5d580fada11fd
Tx public key: dcafb905a38ed228388220aaeda959b028628d919d7f41d9d9048f2d3278944d
Timestamp: 1582514308 Timestamp [UCT]: 2020-02-24 03:18:28 Age [y:d:h:m:s]: 04:313:01:50:46
Block: 71320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1116328 RingCT/type: yes/0
Extra: 01dcafb905a38ed228388220aaeda959b028628d919d7f41d9d9048f2d3278944d02110000000203d36d11000000000000000000

1 output(s) for total of 356.195177597000 dcy

stealth address amount amount idx
00: 0ab2d21b22cb8f545e4d976093ab7738a469e56e574f2d3acd7a8ebb1afb3888 356.195177597000 131755 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": 71330, "vin": [ { "gen": { "height": 71320 } } ], "vout": [ { "amount": 356195177597, "target": { "key": "0ab2d21b22cb8f545e4d976093ab7738a469e56e574f2d3acd7a8ebb1afb3888" } } ], "extra": [ 1, 220, 175, 185, 5, 163, 142, 210, 40, 56, 130, 32, 170, 237, 169, 89, 176, 40, 98, 141, 145, 157, 127, 65, 217, 217, 4, 143, 45, 50, 120, 148, 77, 2, 17, 0, 0, 0, 2, 3, 211, 109, 17, 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