Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae41c962750823ba0c328ae942a1c1b503e3d3f8a92d39e6c5bfd23b5264e68e

Tx prefix hash: fcb9874022c4bedd3da670cbb521cbf9b7811235b15a78b93117acc9624b0efa
Tx public key: 5cae202743b8137c91063915269b9fd8a9507bad713bd13463b87f0e963b4b04
Timestamp: 1702506130 Timestamp [UCT]: 2023-12-13 22:22:10 Age [y:d:h:m:s]: 00:335:15:22:08
Block: 912518 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240341 RingCT/type: yes/0
Extra: 015cae202743b8137c91063915269b9fd8a9507bad713bd13463b87f0e963b4b0402110000000233af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9246fc0b2e378feed19f7c711af36bcb2ef6de47d3393e6807bd1dd3252d9fc 0.600000000000 1369746 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": 912528, "vin": [ { "gen": { "height": 912518 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9246fc0b2e378feed19f7c711af36bcb2ef6de47d3393e6807bd1dd3252d9fc" } } ], "extra": [ 1, 92, 174, 32, 39, 67, 184, 19, 124, 145, 6, 57, 21, 38, 155, 159, 216, 169, 80, 123, 173, 113, 59, 209, 52, 99, 184, 127, 14, 150, 59, 75, 4, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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