Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b0e23f9018e49d9edf8e562bebfe8e4f2e2422247b869ae84b15278879267c4

Tx prefix hash: 65c691265f22ab60e906b8d84f9f7a9897aa4126a6dff07b469f1fd4ba8c7b08
Tx public key: c8dc75afeb2d272bc49618af46949c7bc615024bf32eab2288f1f36e3df73947
Timestamp: 1732692486 Timestamp [UCT]: 2024-11-27 07:28:06 Age [y:d:h:m:s]: 00:117:15:29:50
Block: 1162690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83873 RingCT/type: yes/0
Extra: 01c8dc75afeb2d272bc49618af46949c7bc615024bf32eab2288f1f36e3df739470211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d53e7516d2267e589f65f8729fab1531dff91afd3deb35ff7e96a44ca62c0cf0 0.600000000000 1648347 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": 1162700, "vin": [ { "gen": { "height": 1162690 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d53e7516d2267e589f65f8729fab1531dff91afd3deb35ff7e96a44ca62c0cf0" } } ], "extra": [ 1, 200, 220, 117, 175, 235, 45, 39, 43, 196, 150, 24, 175, 70, 148, 156, 123, 198, 21, 2, 75, 243, 46, 171, 34, 136, 241, 243, 110, 61, 247, 57, 71, 2, 17, 0, 0, 0, 4, 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