Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cc47158cc455380f64ed7ac8bcdf22529c7c12329041c0cde78fa013a9807bb

Tx prefix hash: 25e275dc824e6884465c317b3c27c7a5870ef692b6301f2db6c563e8640d1e18
Tx public key: 1bd0f5cb01fea503ba825ce617ed3b32206551ed4d6e0bbc9aa4c28db6deb6e9
Timestamp: 1707509154 Timestamp [UCT]: 2024-02-09 20:05:54 Age [y:d:h:m:s]: 01:042:09:57:07
Block: 953991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291365 RingCT/type: yes/0
Extra: 011bd0f5cb01fea503ba825ce617ed3b32206551ed4d6e0bbc9aa4c28db6deb6e90211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9760c6f646d3b7b6d8f499322aedde575b98d24f9d6c9e5d7981f445fc8a6d9d 0.600000000000 1413263 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": 954001, "vin": [ { "gen": { "height": 953991 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9760c6f646d3b7b6d8f499322aedde575b98d24f9d6c9e5d7981f445fc8a6d9d" } } ], "extra": [ 1, 27, 208, 245, 203, 1, 254, 165, 3, 186, 130, 92, 230, 23, 237, 59, 50, 32, 101, 81, 237, 77, 110, 11, 188, 154, 164, 194, 141, 182, 222, 182, 233, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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