Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa1474d498ed552cbcf9721cf7f0566a06dd9521e43cbbd3d79bdeda5e48ef41

Tx prefix hash: 260bb1ac19000bd47366084ec3a6a0bc978dbc0bfbee458c4c8a3d5231680c48
Tx public key: c925ceaa407f317419ec6f2d54de33a89e22588f92e85ea6000b75c9c0460c8f
Timestamp: 1711724182 Timestamp [UCT]: 2024-03-29 14:56:22 Age [y:d:h:m:s]: 01:222:10:52:34
Block: 988966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417639 RingCT/type: yes/0
Extra: 01c925ceaa407f317419ec6f2d54de33a89e22588f92e85ea6000b75c9c0460c8f0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1cb820c2aed6d4c897228ff7938bb70925e5e98726e56293abd27db4f84a492 0.600000000000 1449257 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": 988976, "vin": [ { "gen": { "height": 988966 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1cb820c2aed6d4c897228ff7938bb70925e5e98726e56293abd27db4f84a492" } } ], "extra": [ 1, 201, 37, 206, 170, 64, 127, 49, 116, 25, 236, 111, 45, 84, 222, 51, 168, 158, 34, 88, 143, 146, 232, 94, 166, 0, 11, 117, 201, 192, 70, 12, 143, 2, 17, 0, 0, 0, 2, 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