Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10dee967e9c58d279e07da64103f8dafaa0b8f05518ccd58c0f8e36e6e92cf15

Tx prefix hash: 0062600c6f5ece08a2ecc6106894198cd487d20f6d0e4acfbd6ec73d4c60885c
Tx public key: b044346ab89f48011fc3adc32600be9a588d1ece0a55a064d7c4868326ecf5d4
Timestamp: 1730405128 Timestamp [UCT]: 2024-10-31 20:05:28 Age [y:d:h:m:s]: 00:140:04:14:30
Block: 1143735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100034 RingCT/type: yes/0
Extra: 01b044346ab89f48011fc3adc32600be9a588d1ece0a55a064d7c4868326ecf5d40211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e21d602df83ae7e282dfc56f66d2fe22e27692a3b3d9e9adc4168e5f588e4134 0.600000000000 1627710 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": 1143745, "vin": [ { "gen": { "height": 1143735 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e21d602df83ae7e282dfc56f66d2fe22e27692a3b3d9e9adc4168e5f588e4134" } } ], "extra": [ 1, 176, 68, 52, 106, 184, 159, 72, 1, 31, 195, 173, 195, 38, 0, 190, 154, 88, 141, 30, 206, 10, 85, 160, 100, 215, 196, 134, 131, 38, 236, 245, 212, 2, 17, 0, 0, 0, 1, 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