Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c165ca3459f86d4fe75a8f2e7e2aa0d80b404139101f5aa1b1de85bcce2102a7

Tx prefix hash: 66bd31d463db22cfef1bf36fc57ad7275107db1307c4d73036944bd71540ebc2
Tx public key: c9bdfb62ddda939dd4f36646bf20fdeac8ae5df5e5d2204b9e50d74f42d46cf2
Timestamp: 1707120061 Timestamp [UCT]: 2024-02-05 08:01:01 Age [y:d:h:m:s]: 01:023:06:03:57
Block: 950758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277652 RingCT/type: yes/0
Extra: 01c9bdfb62ddda939dd4f36646bf20fdeac8ae5df5e5d2204b9e50d74f42d46cf20211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4186d6fb444edfcc0eecc6ce33467995bc1deb37c658cecb586971cb8cc07ab9 0.600000000000 1409428 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": 950768, "vin": [ { "gen": { "height": 950758 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4186d6fb444edfcc0eecc6ce33467995bc1deb37c658cecb586971cb8cc07ab9" } } ], "extra": [ 1, 201, 189, 251, 98, 221, 218, 147, 157, 212, 243, 102, 70, 191, 32, 253, 234, 200, 174, 93, 245, 229, 210, 32, 75, 158, 80, 215, 79, 66, 212, 108, 242, 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