Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc81ea9eb79c93d5b0e25f78119ca6717c287ff38a39231fdf6f0a903c9ccc72

Tx prefix hash: df0185c5f158187957ad4365a639ef0af4f39a0af96edb429cf3eb481f952c18
Tx public key: 269e9d3a21af5be28b7424e82b7064d235369d091310c57f453792e7ad194ab7
Timestamp: 1717270645 Timestamp [UCT]: 2024-06-01 19:37:25 Age [y:d:h:m:s]: 00:297:01:10:42
Block: 1034935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212281 RingCT/type: yes/0
Extra: 01269e9d3a21af5be28b7424e82b7064d235369d091310c57f453792e7ad194ab70211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5deae1f0f7a46a7c98157038d8353641b5b4d09c460729df3867c6bcde53bc1 0.600000000000 1503454 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": 1034945, "vin": [ { "gen": { "height": 1034935 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5deae1f0f7a46a7c98157038d8353641b5b4d09c460729df3867c6bcde53bc1" } } ], "extra": [ 1, 38, 158, 157, 58, 33, 175, 91, 226, 139, 116, 36, 232, 43, 112, 100, 210, 53, 54, 157, 9, 19, 16, 197, 127, 69, 55, 146, 231, 173, 25, 74, 183, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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