Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cba28c9d7aea8d757009cacb7be7d9cf251d177cadfb64f4f3187bce9f410ef9

Tx prefix hash: 483246aa69639de19819474e87a4d4c5e625e1a8a8c233bb89a1a79120c55569
Tx public key: f9e949acf8e05f70161a597906ea8738ff0ba388d90f9e6455e770b22fd82519
Timestamp: 1734333146 Timestamp [UCT]: 2024-12-16 07:12:26 Age [y:d:h:m:s]: 00:183:17:43:57
Block: 1176292 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131011 RingCT/type: yes/0
Extra: 01f9e949acf8e05f70161a597906ea8738ff0ba388d90f9e6455e770b22fd82519021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a53f09b744ee90b5f8407527e60f99d4b475fd83bf6254b463603f600d061d11 0.600000000000 1662623 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": 1176302, "vin": [ { "gen": { "height": 1176292 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a53f09b744ee90b5f8407527e60f99d4b475fd83bf6254b463603f600d061d11" } } ], "extra": [ 1, 249, 233, 73, 172, 248, 224, 95, 112, 22, 26, 89, 121, 6, 234, 135, 56, 255, 11, 163, 136, 217, 15, 158, 100, 85, 231, 112, 178, 47, 216, 37, 25, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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