Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc5c2a7008f88d130802ec2f36cc152093f3c355b5743a7f06c904f6455ad317

Tx prefix hash: fff687958a0f1da9063db7c6032dbc1dcd707c2cf48c398dccf9c830147377bf
Tx public key: 1d946b116ba33a04329dced2041a71885f7594ad54df724b13cd529dcd2fb69e
Timestamp: 1581515176 Timestamp [UCT]: 2020-02-12 13:46:16 Age [y:d:h:m:s]: 04:288:03:00:14
Block: 63449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1098076 RingCT/type: yes/0
Extra: 011d946b116ba33a04329dced2041a71885f7594ad54df724b13cd529dcd2fb69e0211000000027adf42d3000000000000000000

1 output(s) for total of 378.240420206000 dcy

stealth address amount amount idx
00: f0c366fec1bd5e3722cedeb91e94e14cdebce1628e9e70a315d368cc53335f09 378.240420206000 117003 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": 63459, "vin": [ { "gen": { "height": 63449 } } ], "vout": [ { "amount": 378240420206, "target": { "key": "f0c366fec1bd5e3722cedeb91e94e14cdebce1628e9e70a315d368cc53335f09" } } ], "extra": [ 1, 29, 148, 107, 17, 107, 163, 58, 4, 50, 157, 206, 210, 4, 26, 113, 136, 95, 117, 148, 173, 84, 223, 114, 75, 19, 205, 82, 157, 205, 47, 182, 158, 2, 17, 0, 0, 0, 2, 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