Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 879ef1c50f449176ac38b34db0bf89bcf7599240c0db947a0df3ffbaed3a3911

Tx prefix hash: aa29705389bd80c028bcd6df3cd34f032fc7cb9487a84fce88ebc13ce4d1c1c1
Tx public key: 914ca298e2901b4f61ad4d72f4f53dc2195876480b7f09d6eb49cf2ff311a62a
Timestamp: 1719393062 Timestamp [UCT]: 2024-06-26 09:11:02 Age [y:d:h:m:s]: 00:306:16:10:02
Block: 1052512 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219171 RingCT/type: yes/0
Extra: 01914ca298e2901b4f61ad4d72f4f53dc2195876480b7f09d6eb49cf2ff311a62a0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d87cb96b27862cfeecbdcbff73c1f1101be8bf1b7e5aa696d8bbca77acbe2f3 0.600000000000 1522841 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": 1052522, "vin": [ { "gen": { "height": 1052512 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d87cb96b27862cfeecbdcbff73c1f1101be8bf1b7e5aa696d8bbca77acbe2f3" } } ], "extra": [ 1, 145, 76, 162, 152, 226, 144, 27, 79, 97, 173, 77, 114, 244, 245, 61, 194, 25, 88, 118, 72, 11, 127, 9, 214, 235, 73, 207, 47, 243, 17, 166, 42, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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