Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a73447e6b9a0bc701d1676624dda69d46cd4e9af77ea7df92b0416d36239a070

Tx prefix hash: 57db2261343ac51fc12462ccff54b011c596c81df42e36a5bfdbdf242352858a
Tx public key: d3801201c6b46ae193c8f240b26badfdfe03da90a78877f7e8f3991309189099
Timestamp: 1577946164 Timestamp [UCT]: 2020-01-02 06:22:44 Age [y:d:h:m:s]: 05:131:21:07:36
Block: 36972 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1244058 RingCT/type: yes/0
Extra: 01d3801201c6b46ae193c8f240b26badfdfe03da90a78877f7e8f39913091890990211000000284943cd9f000000000000000000

1 output(s) for total of 462.910752033000 dcy

stealth address amount amount idx
00: af1e083cfe50b1206d3ff1ec9f4845d96cfdee5dcad75a03ea117f3e97c919fb 462.910752033000 62696 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": 36982, "vin": [ { "gen": { "height": 36972 } } ], "vout": [ { "amount": 462910752033, "target": { "key": "af1e083cfe50b1206d3ff1ec9f4845d96cfdee5dcad75a03ea117f3e97c919fb" } } ], "extra": [ 1, 211, 128, 18, 1, 198, 180, 106, 225, 147, 200, 242, 64, 178, 107, 173, 253, 254, 3, 218, 144, 167, 136, 119, 247, 232, 243, 153, 19, 9, 24, 144, 153, 2, 17, 0, 0, 0, 40, 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