Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38f5886e7260e2d39faccfea772f09416979d2f38f861f1c57ec6db4930b123b

Tx prefix hash: 8963da104ae15824a75b48229bb018b65073603838edbf7a5a7007313ca86fee
Tx public key: 542338ec04e1d4be9aa1c36ba9c0f0f84e39d28580793aa1bd51c2b32b615bdf
Timestamp: 1712068699 Timestamp [UCT]: 2024-04-02 14:38:19 Age [y:d:h:m:s]: 00:348:12:18:04
Block: 991767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249207 RingCT/type: yes/0
Extra: 01542338ec04e1d4be9aa1c36ba9c0f0f84e39d28580793aa1bd51c2b32b615bdf0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e89596ac2ccc70a9dd665972dc3dea82efb3b5ad1ec6b334c1b5710bff885098 0.600000000000 1452103 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": 991777, "vin": [ { "gen": { "height": 991767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e89596ac2ccc70a9dd665972dc3dea82efb3b5ad1ec6b334c1b5710bff885098" } } ], "extra": [ 1, 84, 35, 56, 236, 4, 225, 212, 190, 154, 161, 195, 107, 169, 192, 240, 248, 78, 57, 210, 133, 128, 121, 58, 161, 189, 81, 194, 179, 43, 97, 91, 223, 2, 17, 0, 0, 0, 5, 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