Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65556051fd06fbf123cfc82a01ea1c57361590eaef59b1c24c4955a574f9f84f

Tx prefix hash: ce739229d7ee579511f971928ccfe73088564fa5f03fd6c6610f0f438f43a967
Tx public key: b0ace82bcead256f0d17f1f017d0f226cf3b36e538addc602536feea86f9b679
Timestamp: 1696310279 Timestamp [UCT]: 2023-10-03 05:17:59 Age [y:d:h:m:s]: 01:220:04:13:49
Block: 861365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 418416 RingCT/type: yes/0
Extra: 01b0ace82bcead256f0d17f1f017d0f226cf3b36e538addc602536feea86f9b679021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.858895298000 dcy

stealth address amount amount idx
00: 3a2aba357d084f4af14e44931db070d2bf310cbd4db7e7ed06f9824d57319805 0.858895298000 1315705 of 0

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": 861375, "vin": [ { "gen": { "height": 861365 } } ], "vout": [ { "amount": 858895298, "target": { "key": "3a2aba357d084f4af14e44931db070d2bf310cbd4db7e7ed06f9824d57319805" } } ], "extra": [ 1, 176, 172, 232, 43, 206, 173, 37, 111, 13, 23, 241, 240, 23, 208, 242, 38, 207, 59, 54, 229, 56, 173, 220, 96, 37, 54, 254, 234, 134, 249, 182, 121, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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