Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5ab94770cd3444a5fd74c4256cd1befbbaf4d588bcd1e17837c9bef8b91faac

Tx prefix hash: b0f332e6e1e814897060136348fbdf19f6fe7dfeeae0523840ca184f23b968e5
Tx public key: c20486afe7d0ffb6139910f2db689632c0decd0a94ce74379f18cc4e8bc67ac4
Timestamp: 1694905906 Timestamp [UCT]: 2023-09-16 23:11:46 Age [y:d:h:m:s]: 01:165:20:28:54
Block: 849697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379599 RingCT/type: yes/0
Extra: 01c20486afe7d0ffb6139910f2db689632c0decd0a94ce74379f18cc4e8bc67ac40211000000034b8f5122000000000000000000

1 output(s) for total of 0.938860721000 dcy

stealth address amount amount idx
00: 9cae3c31d20626b243990becfeeec7eff6956c2081fd8dc6108b2c8cceefe6a1 0.938860721000 1303373 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": 849707, "vin": [ { "gen": { "height": 849697 } } ], "vout": [ { "amount": 938860721, "target": { "key": "9cae3c31d20626b243990becfeeec7eff6956c2081fd8dc6108b2c8cceefe6a1" } } ], "extra": [ 1, 194, 4, 134, 175, 231, 208, 255, 182, 19, 153, 16, 242, 219, 104, 150, 50, 192, 222, 205, 10, 148, 206, 116, 55, 159, 24, 204, 78, 139, 198, 122, 196, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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