Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f0b5ce2c76c81234efd2523c9b398cbbcf0153817f1e7a398ed59d528a56dd3

Tx prefix hash: a8fdb61abd9bb7fb633ee5caa1de34469162fcc9c548c9af9c0de7f69d62f1dc
Tx public key: 261dfcb894bb77dcdccd185e9a279432785829f628efb01310ed3e03570788a5
Timestamp: 1583540901 Timestamp [UCT]: 2020-03-07 00:28:21 Age [y:d:h:m:s]: 04:306:23:27:14
Block: 78036 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1113747 RingCT/type: yes/0
Extra: 01261dfcb894bb77dcdccd185e9a279432785829f628efb01310ed3e03570788a50211000000304943cd9f000000000000000000

1 output(s) for total of 338.403721589000 dcy

stealth address amount amount idx
00: 049ef4678a2c989e40094a672334186e2f84ce5939677258d2ccd553655f762c 338.403721589000 143293 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": 78046, "vin": [ { "gen": { "height": 78036 } } ], "vout": [ { "amount": 338403721589, "target": { "key": "049ef4678a2c989e40094a672334186e2f84ce5939677258d2ccd553655f762c" } } ], "extra": [ 1, 38, 29, 252, 184, 148, 187, 119, 220, 220, 205, 24, 94, 154, 39, 148, 50, 120, 88, 41, 246, 40, 239, 176, 19, 16, 237, 62, 3, 87, 7, 136, 165, 2, 17, 0, 0, 0, 48, 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