Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4a2b392fdf27097e26054ce4ebd7f3861f5a088d6ec67fb968ec6ed697dfaec

Tx prefix hash: 115da01e92ecc9b62310e7fc6b978586f3d2b1d89ae2bbf6c18e40b142cc0151
Tx public key: ba15072bb59043d3797dde97b52c9e7e75882a175ce04137e5c486e9e75c4bfb
Timestamp: 1581091061 Timestamp [UCT]: 2020-02-07 15:57:41 Age [y:d:h:m:s]: 04:343:20:37:50
Block: 60698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1137188 RingCT/type: yes/0
Extra: 01ba15072bb59043d3797dde97b52c9e7e75882a175ce04137e5c486e9e75c4bfb0211000000037adf42d3000000000000000000

1 output(s) for total of 386.276053043000 dcy

stealth address amount amount idx
00: a6a62ae0c3c5f20561d94ccd091eeb58bcdcf7ebf47474acd49b42cad1fcf35b 386.276053043000 111744 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": 60708, "vin": [ { "gen": { "height": 60698 } } ], "vout": [ { "amount": 386276053043, "target": { "key": "a6a62ae0c3c5f20561d94ccd091eeb58bcdcf7ebf47474acd49b42cad1fcf35b" } } ], "extra": [ 1, 186, 21, 7, 43, 181, 144, 67, 211, 121, 125, 222, 151, 181, 44, 158, 126, 117, 136, 42, 23, 92, 224, 65, 55, 229, 196, 134, 233, 231, 92, 75, 251, 2, 17, 0, 0, 0, 3, 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