Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 853a6cdb1a1decc15ef9e8833ac74d4f6b4f3708e18529a1211108facbaaf9a1

Tx prefix hash: cf9a9f5556b3527a84f2d3b54d44cd2cfa050a885003336c2b06e1405d355557
Tx public key: ade93af5a53014e32fd973dfe4d363246f8ab92984e030915c809fe0c4266f0c
Timestamp: 1639464277 Timestamp [UCT]: 2021-12-14 06:44:37 Age [y:d:h:m:s]: 03:322:11:00:31
Block: 395160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1006932 RingCT/type: yes/0
Extra: 01ade93af5a53014e32fd973dfe4d363246f8ab92984e030915c809fe0c4266f0c021100000004408d5ef5000000000000000000

1 output(s) for total of 30.107260467000 dcy

stealth address amount amount idx
00: d29e09b67de33daa7fe719812158202dc50f722d71dcc76dffec225fcb0cf021 30.107260467000 792987 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": 395170, "vin": [ { "gen": { "height": 395160 } } ], "vout": [ { "amount": 30107260467, "target": { "key": "d29e09b67de33daa7fe719812158202dc50f722d71dcc76dffec225fcb0cf021" } } ], "extra": [ 1, 173, 233, 58, 245, 165, 48, 20, 227, 47, 217, 115, 223, 228, 211, 99, 36, 111, 138, 185, 41, 132, 224, 48, 145, 92, 128, 159, 224, 196, 38, 111, 12, 2, 17, 0, 0, 0, 4, 64, 141, 94, 245, 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