Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca8a0a38eca3f08757340aaff8d85333c5c9377e8d2b0c500d349bab66c286d2

Tx prefix hash: 5845801edf298bbc59ef23354fe251eb6307932eec9fd8848367ec69f040b5bc
Tx public key: 68ed560de8f3aa19795077d09aa1edc8c93a0719c8cdd4f8bca8f0ac382180a7
Timestamp: 1714954784 Timestamp [UCT]: 2024-05-06 00:19:44 Age [y:d:h:m:s]: 00:363:10:22:13
Block: 1015732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259795 RingCT/type: yes/0
Extra: 0168ed560de8f3aa19795077d09aa1edc8c93a0719c8cdd4f8bca8f0ac382180a702110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 068f9f9d23428f4a267cc229a75a68b4e91486cdcb75a6ae2d59874bf40b7a01 0.600000000000 1479171 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": 1015742, "vin": [ { "gen": { "height": 1015732 } } ], "vout": [ { "amount": 600000000, "target": { "key": "068f9f9d23428f4a267cc229a75a68b4e91486cdcb75a6ae2d59874bf40b7a01" } } ], "extra": [ 1, 104, 237, 86, 13, 232, 243, 170, 25, 121, 80, 119, 208, 154, 161, 237, 200, 201, 58, 7, 25, 200, 205, 212, 248, 188, 168, 240, 172, 56, 33, 128, 167, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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