Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8d85ccbd02f4acea2c1b60c295d40c47afb89a1f78d06c8ced130112812d0db

Tx prefix hash: 95ba576cf39f7a743ac9f3efdda54daf674a2c56f3776c1f997e9c2e539eda5f
Tx public key: fd7118616280240cc442090d8c02ec109eddb263f43fbfb06c012649a5d6c8e7
Timestamp: 1695561646 Timestamp [UCT]: 2023-09-24 13:20:46 Age [y:d:h:m:s]: 01:153:09:42:33
Block: 855150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370667 RingCT/type: yes/0
Extra: 01fd7118616280240cc442090d8c02ec109eddb263f43fbfb06c012649a5d6c8e7021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.900602420000 dcy

stealth address amount amount idx
00: 7b1c290be92c8788ba17bab18ecaff280839bb862032409a5eef6b4ce81f6341 0.900602420000 1309154 of 0

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": 855160, "vin": [ { "gen": { "height": 855150 } } ], "vout": [ { "amount": 900602420, "target": { "key": "7b1c290be92c8788ba17bab18ecaff280839bb862032409a5eef6b4ce81f6341" } } ], "extra": [ 1, 253, 113, 24, 97, 98, 128, 36, 12, 196, 66, 9, 13, 140, 2, 236, 16, 158, 221, 178, 99, 244, 63, 191, 176, 108, 1, 38, 73, 165, 214, 200, 231, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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