Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbf46e9c7a32151e534dd7bdb4aa226d8368b43871207f41c32dc6e31abeae5d

Tx prefix hash: 571cd20235ea9351099dadfe58d336bd9ae3c02cd7bb429ad1de03c4dee0d91f
Tx public key: 1d0808ab1a93c7c4b853b261df4e08fb11fdbb1234bb636108ac1be3cd025689
Timestamp: 1732818837 Timestamp [UCT]: 2024-11-28 18:33:57 Age [y:d:h:m:s]: 01:035:20:16:08
Block: 1163733 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284087 RingCT/type: yes/0
Extra: 011d0808ab1a93c7c4b853b261df4e08fb11fdbb1234bb636108ac1be3cd0256890211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77a13c6b43629e5b9ac1836a444bdabeddd18cf3a95577c7911329ed685f1ee0 0.600000000000 1649402 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": 1163743, "vin": [ { "gen": { "height": 1163733 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77a13c6b43629e5b9ac1836a444bdabeddd18cf3a95577c7911329ed685f1ee0" } } ], "extra": [ 1, 29, 8, 8, 171, 26, 147, 199, 196, 184, 83, 178, 97, 223, 78, 8, 251, 17, 253, 187, 18, 52, 187, 99, 97, 8, 172, 27, 227, 205, 2, 86, 137, 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