Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9c72ce1ecc74814d822aa4c2274695a0b47b1ee082ab0486cffa31229f6510f

Tx prefix hash: 4c76145cb2038082983631df2b07cfece3f5fe35f259eaf21f30654c7ba66ace
Tx public key: 42c725729e949c9276165e7407d2e8ccd4ae7058b161b065f46eab3b7a12f85b
Timestamp: 1696105575 Timestamp [UCT]: 2023-09-30 20:26:15 Age [y:d:h:m:s]: 01:189:13:28:59
Block: 859660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396524 RingCT/type: yes/0
Extra: 0142c725729e949c9276165e7407d2e8ccd4ae7058b161b065f46eab3b7a12f85b021100000007bfa22221000000000000000000

1 output(s) for total of 0.870140936000 dcy

stealth address amount amount idx
00: 38f55f123d0747adc3bd93fdb328392d9c1021bc8093dab66408aeea2ae7b804 0.870140936000 1313898 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": 859670, "vin": [ { "gen": { "height": 859660 } } ], "vout": [ { "amount": 870140936, "target": { "key": "38f55f123d0747adc3bd93fdb328392d9c1021bc8093dab66408aeea2ae7b804" } } ], "extra": [ 1, 66, 199, 37, 114, 158, 148, 156, 146, 118, 22, 94, 116, 7, 210, 232, 204, 212, 174, 112, 88, 177, 97, 176, 101, 244, 110, 171, 59, 122, 18, 248, 91, 2, 17, 0, 0, 0, 7, 191, 162, 34, 33, 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