Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc9a16278bb1ade0bd3eeab978a736a8403ece29ee10fdf6601cdbe201f23048

Tx prefix hash: f8e1708671dc9df63f50b630e7493e4adf234706e8ca5bf330c0cd0de2147b91
Tx public key: d56dceee2fa18791f3c84b8252ac77dae513acf3db245a570d55ebd21579c84b
Timestamp: 1739471574 Timestamp [UCT]: 2025-02-13 18:32:54 Age [y:d:h:m:s]: 00:346:15:34:24
Block: 1218555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245404 RingCT/type: yes/0
Extra: 01d56dceee2fa18791f3c84b8252ac77dae513acf3db245a570d55ebd21579c84b021100000010007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6dfae31c85d7edb4a4c512349ec1dc6c685c9f50ccf2448a8a4c8681b87faebd 0.600000000000 1705374 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": 1218565, "vin": [ { "gen": { "height": 1218555 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6dfae31c85d7edb4a4c512349ec1dc6c685c9f50ccf2448a8a4c8681b87faebd" } } ], "extra": [ 1, 213, 109, 206, 238, 47, 161, 135, 145, 243, 200, 75, 130, 82, 172, 119, 218, 229, 19, 172, 243, 219, 36, 90, 87, 13, 85, 235, 210, 21, 121, 200, 75, 2, 17, 0, 0, 0, 16, 0, 127, 151, 138, 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