Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5048f61a2176c00cfe82a8c69ecd22c488a853281815f68e64625e115d525ea

Tx prefix hash: 966d5377d30397efc9a1852fa63868f35c2965bff94f2236c8b93fd51758cbbb
Tx public key: c7c5bc831ea911af892eb1d1ad35b7f4f7f51679bb1156b701b34850febe737c
Timestamp: 1733467771 Timestamp [UCT]: 2024-12-06 06:49:31 Age [y:d:h:m:s]: 00:150:16:10:42
Block: 1169104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107505 RingCT/type: yes/0
Extra: 01c7c5bc831ea911af892eb1d1ad35b7f4f7f51679bb1156b701b34850febe737c0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a77ae29e91da7efadd4bf973ffad9c0514a20e6639746ea2dd5b9a3c40d996f0 0.600000000000 1654817 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": 1169114, "vin": [ { "gen": { "height": 1169104 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a77ae29e91da7efadd4bf973ffad9c0514a20e6639746ea2dd5b9a3c40d996f0" } } ], "extra": [ 1, 199, 197, 188, 131, 30, 169, 17, 175, 137, 46, 177, 209, 173, 53, 183, 244, 247, 245, 22, 121, 187, 17, 86, 183, 1, 179, 72, 80, 254, 190, 115, 124, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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