Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c28c1331b75afae2af8aa4cd2d7b558fa6cf9386a853b9cf0dfee86a34d0dfb8

Tx prefix hash: d11678e51bfeb24e8a4eea4d32eac9d41e755ab5f5a6f5125c9a635285cc2ee7
Tx public key: 43771fc26700c45125b2bf9c1e88ac8e1611f7771ba5d41f26f9c3696947f2ee
Timestamp: 1736446448 Timestamp [UCT]: 2025-01-09 18:14:08 Age [y:d:h:m:s]: 00:067:23:46:30
Block: 1193763 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48382 RingCT/type: yes/0
Extra: 0143771fc26700c45125b2bf9c1e88ac8e1611f7771ba5d41f26f9c3696947f2ee0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53093449500e9191fc5cc419b83718aa87c350a921f0ca2456e9f8986e82f0c5 0.600000000000 1680328 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": 1193773, "vin": [ { "gen": { "height": 1193763 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53093449500e9191fc5cc419b83718aa87c350a921f0ca2456e9f8986e82f0c5" } } ], "extra": [ 1, 67, 119, 31, 194, 103, 0, 196, 81, 37, 178, 191, 156, 30, 136, 172, 142, 22, 17, 247, 119, 27, 165, 212, 31, 38, 249, 195, 105, 105, 71, 242, 238, 2, 17, 0, 0, 0, 6, 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