Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47c099d2e6d7931f6c93941f1307def2670504ff858786d3bd46576b1f81b76f

Tx prefix hash: 65b5b9604af97ee29cb84537524f46b6cd0ac3f77b6807ac3c38bc8a17ec1a8f
Tx public key: 696bdfea7885a9a212abdb1f5f95b5543fa9fb39ec5e2320645a3968d01739a7
Timestamp: 1734931564 Timestamp [UCT]: 2024-12-23 05:26:04 Age [y:d:h:m:s]: 00:176:16:01:50
Block: 1181256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125951 RingCT/type: yes/0
Extra: 01696bdfea7885a9a212abdb1f5f95b5543fa9fb39ec5e2320645a3968d01739a7021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d5f447258f739f9b474791c9ef3e3f42f1d54ecde0757125a15df8c9e7838ef 0.600000000000 1667673 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": 1181266, "vin": [ { "gen": { "height": 1181256 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d5f447258f739f9b474791c9ef3e3f42f1d54ecde0757125a15df8c9e7838ef" } } ], "extra": [ 1, 105, 107, 223, 234, 120, 133, 169, 162, 18, 171, 219, 31, 95, 149, 181, 84, 63, 169, 251, 57, 236, 94, 35, 32, 100, 90, 57, 104, 208, 23, 57, 167, 2, 17, 0, 0, 0, 2, 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