Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc69322b3bbe0865aed50a802b54229e99de6bcc3f0a89c0441d2caca17e1c9b

Tx prefix hash: 8549d2214917dee0633c8a9a1e47908e4da67de5e5ae0d25efb24b9c072abc61
Tx public key: aec8085291dd14253a0aa0acb66b5eb7ca8138472244c18dbf4145a882ce83fa
Timestamp: 1584922932 Timestamp [UCT]: 2020-03-23 00:22:12 Age [y:d:h:m:s]: 04:281:14:14:32
Block: 86947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1098116 RingCT/type: yes/0
Extra: 01aec8085291dd14253a0aa0acb66b5eb7ca8138472244c18dbf4145a882ce83fa021100000022d81c26c0000000000000000000

1 output(s) for total of 316.183052549000 dcy

stealth address amount amount idx
00: 57210ce8b52e2ec463a9495fa9de6fa28e244b7722f69d69abbeb53a4e279a32 316.183052549000 156799 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": 86957, "vin": [ { "gen": { "height": 86947 } } ], "vout": [ { "amount": 316183052549, "target": { "key": "57210ce8b52e2ec463a9495fa9de6fa28e244b7722f69d69abbeb53a4e279a32" } } ], "extra": [ 1, 174, 200, 8, 82, 145, 221, 20, 37, 58, 10, 160, 172, 182, 107, 94, 183, 202, 129, 56, 71, 34, 68, 193, 141, 191, 65, 69, 168, 130, 206, 131, 250, 2, 17, 0, 0, 0, 34, 216, 28, 38, 192, 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