Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69d3d44a27536badeacaf100c26c5f6bac4dbb69ec212f837bac04808fd4a9e6

Tx prefix hash: 01d3c93a27fdf9dca483e633392d9b49bf1cbe6e1b807ed32dbb841fed90904c
Tx public key: 8dca4e401ad3f1779b5c1dc3a825108586b73a7769fd56cba7ab371c29d731d7
Timestamp: 1718803601 Timestamp [UCT]: 2024-06-19 13:26:41 Age [y:d:h:m:s]: 00:357:07:09:42
Block: 1047642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255356 RingCT/type: yes/0
Extra: 018dca4e401ad3f1779b5c1dc3a825108586b73a7769fd56cba7ab371c29d731d702110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a644b28c4850447292042fafedb7ac95961a9d6853c86c42cfae00828a971dfa 0.600000000000 1517517 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": 1047652, "vin": [ { "gen": { "height": 1047642 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a644b28c4850447292042fafedb7ac95961a9d6853c86c42cfae00828a971dfa" } } ], "extra": [ 1, 141, 202, 78, 64, 26, 211, 241, 119, 155, 92, 29, 195, 168, 37, 16, 133, 134, 183, 58, 119, 105, 253, 86, 203, 167, 171, 55, 28, 41, 215, 49, 215, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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