Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c50e08b0dede7c316b58e5e214c8edb900c11297488836ad571d82a4373dfdc

Tx prefix hash: c0add223a0c3b5f450c132bfa066ef22f3e5e41aac8ae14926638976fa7af29e
Tx public key: 9465fde5a894b574f0fa1fae8f6b21ecc3e7b31d65b81ef76046c85a93470ed7
Timestamp: 1709003030 Timestamp [UCT]: 2024-02-27 03:03:50 Age [y:d:h:m:s]: 01:038:18:52:28
Block: 966398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288718 RingCT/type: yes/0
Extra: 019465fde5a894b574f0fa1fae8f6b21ecc3e7b31d65b81ef76046c85a93470ed70211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b908d0bbd21a0af5aaafdbefdc518de025acb34afac5ff4ddde7e5cb04f9557 0.600000000000 1426155 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": 966408, "vin": [ { "gen": { "height": 966398 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b908d0bbd21a0af5aaafdbefdc518de025acb34afac5ff4ddde7e5cb04f9557" } } ], "extra": [ 1, 148, 101, 253, 229, 168, 148, 181, 116, 240, 250, 31, 174, 143, 107, 33, 236, 195, 231, 179, 29, 101, 184, 30, 247, 96, 70, 200, 90, 147, 71, 14, 215, 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