Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65bef21829aa1ef55cd28f00816555d299b6eedaef94a9b3ce4cdcfb3b6d4cdf

Tx prefix hash: 27822d338e2e39360f72fa46e9685e6a013afec1a78715ae9d23c5c14041c994
Tx public key: ad27c15571047190aaf5f081e4a18fde0bd409e06cd6a42abc3da55d07a339ed
Timestamp: 1735213186 Timestamp [UCT]: 2024-12-26 11:39:46 Age [y:d:h:m:s]: 00:095:17:31:23
Block: 1183569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68193 RingCT/type: yes/0
Extra: 01ad27c15571047190aaf5f081e4a18fde0bd409e06cd6a42abc3da55d07a339ed0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34630f28c5fdce88c259dd8bf8667abd6d3c210d3bd494f0e4b3edef3fec337c 0.600000000000 1670014 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": 1183579, "vin": [ { "gen": { "height": 1183569 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34630f28c5fdce88c259dd8bf8667abd6d3c210d3bd494f0e4b3edef3fec337c" } } ], "extra": [ 1, 173, 39, 193, 85, 113, 4, 113, 144, 170, 245, 240, 129, 228, 161, 143, 222, 11, 212, 9, 224, 108, 214, 164, 42, 188, 61, 165, 93, 7, 163, 57, 237, 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