Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: daadfc4feef1fd5b889d7e442ac53db8f5d5e819a1012aee0660a0298fb5bcc9

Tx prefix hash: c0532c6159123e25ab948b592fc93d11fbc1585345831c22e001f29e8893f666
Tx public key: 6079fb14407276589f2a0adf65b5c1c343666822a03fd123740af1a63cfb36b5
Timestamp: 1581248980 Timestamp [UCT]: 2020-02-09 11:49:40 Age [y:d:h:m:s]: 04:330:11:50:40
Block: 61310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1128328 RingCT/type: yes/0
Extra: 016079fb14407276589f2a0adf65b5c1c343666822a03fd123740af1a63cfb36b50211000002567adf42d3000000000000000000

1 output(s) for total of 384.463694893000 dcy

stealth address amount amount idx
00: 9ad710b31f558a0bf761ff582f38e61a8c673ad9135d8a8d74d9294f93da557e 384.463694893000 112981 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": 61320, "vin": [ { "gen": { "height": 61310 } } ], "vout": [ { "amount": 384463694893, "target": { "key": "9ad710b31f558a0bf761ff582f38e61a8c673ad9135d8a8d74d9294f93da557e" } } ], "extra": [ 1, 96, 121, 251, 20, 64, 114, 118, 88, 159, 42, 10, 223, 101, 181, 193, 195, 67, 102, 104, 34, 160, 63, 209, 35, 116, 10, 241, 166, 60, 251, 54, 181, 2, 17, 0, 0, 2, 86, 122, 223, 66, 211, 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