Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb854cc05e69ddb208e346ae926b8bd8c0f1ea2ad4be2910b0032aa646297d7d

Tx prefix hash: 45229d11728eb63dca6240238850981a171f42494b012d733e532fc0d353de3b
Tx public key: b976289a47ca01c6284670d36f7a130ea0ae7563db5d2337c45b7ecfe82425c3
Timestamp: 1714025041 Timestamp [UCT]: 2024-04-25 06:04:01 Age [y:d:h:m:s]: 00:251:06:03:11
Block: 1008009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179851 RingCT/type: yes/0
Extra: 01b976289a47ca01c6284670d36f7a130ea0ae7563db5d2337c45b7ecfe82425c30211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 652f116a0e401c4f75ecf30e328ed9844fab1eaecbab1e783d7a9909ad523f84 0.600000000000 1469475 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": 1008019, "vin": [ { "gen": { "height": 1008009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "652f116a0e401c4f75ecf30e328ed9844fab1eaecbab1e783d7a9909ad523f84" } } ], "extra": [ 1, 185, 118, 40, 154, 71, 202, 1, 198, 40, 70, 112, 211, 111, 122, 19, 14, 160, 174, 117, 99, 219, 93, 35, 55, 196, 91, 126, 207, 232, 36, 37, 195, 2, 17, 0, 0, 0, 2, 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