Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eed8c7a6c4988a55d6e29851263cdcac0eecb889f6af668b5e1751fc57a8add0

Tx prefix hash: cc8fea2615434f12fcc9c5eb6793c27b066067e8b333494feb0f4413a5567784
Tx public key: 0a6f6f736f476746ae60c89e1061971756a1fafb4da4adea51217aaad368e3a6
Timestamp: 1736302160 Timestamp [UCT]: 2025-01-08 02:09:20 Age [y:d:h:m:s]: 00:300:12:39:18
Block: 1192574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212281 RingCT/type: yes/0
Extra: 010a6f6f736f476746ae60c89e1061971756a1fafb4da4adea51217aaad368e3a6021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5fe01b07f65bef21a2f696c79eacf55d7495136bd258d06e93e72d3e226af55c 0.600000000000 1679127 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": 1192584, "vin": [ { "gen": { "height": 1192574 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5fe01b07f65bef21a2f696c79eacf55d7495136bd258d06e93e72d3e226af55c" } } ], "extra": [ 1, 10, 111, 111, 115, 111, 71, 103, 70, 174, 96, 200, 158, 16, 97, 151, 23, 86, 161, 250, 251, 77, 164, 173, 234, 81, 33, 122, 170, 211, 104, 227, 166, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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