Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8928720eb0cf492a5a6d2e2d94a26e2d32baed394ada36f4b71ec7949343fc2c

Tx prefix hash: a1bd325d42575915707195237aed2f99c0fbaa7ace5e904780bc71d858ba083b
Tx public key: 71e2fb075044b3cb977f9a353f337f23e9b31be1bfc2c4414e7b0392eb296111
Timestamp: 1708623587 Timestamp [UCT]: 2024-02-22 17:39:47 Age [y:d:h:m:s]: 01:264:03:25:26
Block: 963237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 447527 RingCT/type: yes/0
Extra: 0171e2fb075044b3cb977f9a353f337f23e9b31be1bfc2c4414e7b0392eb29611102110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac1ef7df8e0ec1ddff3eb8586ca5d49faf7a6d5a438b5a1846c3c32d0dfe3be0 0.600000000000 1422938 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": 963247, "vin": [ { "gen": { "height": 963237 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac1ef7df8e0ec1ddff3eb8586ca5d49faf7a6d5a438b5a1846c3c32d0dfe3be0" } } ], "extra": [ 1, 113, 226, 251, 7, 80, 68, 179, 203, 151, 127, 154, 53, 63, 51, 127, 35, 233, 179, 27, 225, 191, 194, 196, 65, 78, 123, 3, 146, 235, 41, 97, 17, 2, 17, 0, 0, 0, 5, 89, 218, 211, 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