Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d30b95773286ec10225c9d72c8ca928e387b5f3ca3aabf3b25c1f4df578e3b9

Tx prefix hash: 93de0bf8e53c4a06fc6c00e900544d9135fc4fe67bf6f9b0a0fcf0381a082fb2
Tx public key: 0e162c5a50010e57678ed78801852ecc8b4cb97127f74049cefe87f5c332440c
Timestamp: 1708843751 Timestamp [UCT]: 2024-02-25 06:49:11 Age [y:d:h:m:s]: 01:020:20:09:50
Block: 965069 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275906 RingCT/type: yes/0
Extra: 010e162c5a50010e57678ed78801852ecc8b4cb97127f74049cefe87f5c332440c0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e1d95791f8585fb37f8841a8af5ecc217163491ea9785fb8373b0c91aba6561 0.600000000000 1424816 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": 965079, "vin": [ { "gen": { "height": 965069 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e1d95791f8585fb37f8841a8af5ecc217163491ea9785fb8373b0c91aba6561" } } ], "extra": [ 1, 14, 22, 44, 90, 80, 1, 14, 87, 103, 142, 215, 136, 1, 133, 46, 204, 139, 76, 185, 113, 39, 247, 64, 73, 206, 254, 135, 245, 195, 50, 68, 12, 2, 17, 0, 0, 0, 3, 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