Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4843e704ade66e2e3c36679d3806ed08f9609eead565a76f260e20ce6c1412ea

Tx prefix hash: 572c3b0ad7dbb3c236b49e4c89d701032b9ed59f6f1aa009d4a9452d8aca5a38
Tx public key: b61bc4b62831c0d5098026956a7a75c4c5d338f70aee19bc554358c948099556
Timestamp: 1709099334 Timestamp [UCT]: 2024-02-28 05:48:54 Age [y:d:h:m:s]: 01:034:13:29:44
Block: 967192 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285699 RingCT/type: yes/0
Extra: 01b61bc4b62831c0d5098026956a7a75c4c5d338f70aee19bc554358c9480995560211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e15b72d52d50c47bea5029ad869f74b6f0090eb2c58c0bb54475125ca65a03d 0.600000000000 1426963 of 15

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": 967202, "vin": [ { "gen": { "height": 967192 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e15b72d52d50c47bea5029ad869f74b6f0090eb2c58c0bb54475125ca65a03d" } } ], "extra": [ 1, 182, 27, 196, 182, 40, 49, 192, 213, 9, 128, 38, 149, 106, 122, 117, 196, 197, 211, 56, 247, 10, 238, 25, 188, 85, 67, 88, 201, 72, 9, 149, 86, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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