Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63d6d645bcddfba94b7e3975b614f971ceb02f08309240e8ea7c6902e7e96f1e

Tx prefix hash: 0e2cf698cbe88675a45b5f96e08bd6639e60960b27d7a11881e6c85d74ce29c6
Tx public key: be3bde1fee1af0c600533d014a1e54eefabaf2ec8ccdeb29aa05f3bcdb3b7317
Timestamp: 1697336448 Timestamp [UCT]: 2023-10-15 02:20:48 Age [y:d:h:m:s]: 01:174:02:22:41
Block: 869869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385456 RingCT/type: yes/0
Extra: 01be3bde1fee1af0c600533d014a1e54eefabaf2ec8ccdeb29aa05f3bcdb3b731702110000000136a45730000000000000000000

1 output(s) for total of 0.804938927000 dcy

stealth address amount amount idx
00: 5d912b6826c20bec350e3da3a8f53ed86505e78866464e95fa90ac8e20f0a3d6 0.804938927000 1324732 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": 869879, "vin": [ { "gen": { "height": 869869 } } ], "vout": [ { "amount": 804938927, "target": { "key": "5d912b6826c20bec350e3da3a8f53ed86505e78866464e95fa90ac8e20f0a3d6" } } ], "extra": [ 1, 190, 59, 222, 31, 238, 26, 240, 198, 0, 83, 61, 1, 74, 30, 84, 238, 250, 186, 242, 236, 140, 205, 235, 41, 170, 5, 243, 188, 219, 59, 115, 23, 2, 17, 0, 0, 0, 1, 54, 164, 87, 48, 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