Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d20424940f88e6c6feab0ee5b7689d1cd5e29ead3555483bc6caed1b6039363

Tx prefix hash: b68f6cac7f03069ce0324c18cc34c05cca82644c0004033fc4c11c28f793be23
Tx public key: 859c5ae0ad268674f9a0c7243748125bcd7fe72a5118642b874d47ea2e137cb2
Timestamp: 1703584202 Timestamp [UCT]: 2023-12-26 09:50:02 Age [y:d:h:m:s]: 01:342:08:47:10
Block: 921459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 503558 RingCT/type: yes/0
Extra: 01859c5ae0ad268674f9a0c7243748125bcd7fe72a5118642b874d47ea2e137cb202110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 307a1f699fb4f5d4e1e43ac1691ba84f7ad7e52fd5f24e07908d830463e05032 0.600000000000 1379147 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": 921469, "vin": [ { "gen": { "height": 921459 } } ], "vout": [ { "amount": 600000000, "target": { "key": "307a1f699fb4f5d4e1e43ac1691ba84f7ad7e52fd5f24e07908d830463e05032" } } ], "extra": [ 1, 133, 156, 90, 224, 173, 38, 134, 116, 249, 160, 199, 36, 55, 72, 18, 91, 205, 127, 231, 42, 81, 24, 100, 43, 135, 77, 71, 234, 46, 19, 124, 178, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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