Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9ca94c9f86d4243db72f2784a82ae41ef249c0d9b31aa7e42123ee9e3273362e

Tx prefix hash: aab9ba53f2afbb3749adf9c48e5413c5690a061e4812eee1d191542cc2869755
Tx public key: c509d2e020540b07739f5b50f3f5584c25d3c756b181fc354899ed80dc11b08f
Timestamp: 1583528450 Timestamp [UCT]: 2020-03-06 21:00:50 Age [y:d:h:m:s]: 04:360:00:05:49
Block: 77572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1151766 RingCT/type: yes/0
Extra: 01c509d2e020540b07739f5b50f3f5584c25d3c756b181fc354899ed80dc11b08f0211000000098a2ee0d9000000000000000000

1 output(s) for total of 339.603811490000 dcy

stealth address amount amount idx
00: 280ee07920589714208f176ac41e1afc537598457166905a0cba17874c23546a 339.603811490000 142713 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": 77582, "vin": [ { "gen": { "height": 77572 } } ], "vout": [ { "amount": 339603811490, "target": { "key": "280ee07920589714208f176ac41e1afc537598457166905a0cba17874c23546a" } } ], "extra": [ 1, 197, 9, 210, 224, 32, 84, 11, 7, 115, 159, 91, 80, 243, 245, 88, 76, 37, 211, 199, 86, 177, 129, 252, 53, 72, 153, 237, 128, 220, 17, 176, 143, 2, 17, 0, 0, 0, 9, 138, 46, 224, 217, 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