Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f2c15be97eb85847227a6722a19547cce075f68c7b28a78617c8363fb0022e3

Tx prefix hash: 7e914b9d91f13bfa772b9e512ff9850438dde4d28ea8e43c1664e76d0c70bd51
Tx public key: 3261d30c1181af1ced492e13b9ce40e1897b9c684a0bd0e87de87e66d2dc5f1f
Timestamp: 1706306164 Timestamp [UCT]: 2024-01-26 21:56:04 Age [y:d:h:m:s]: 01:070:01:53:26
Block: 943995 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311177 RingCT/type: yes/0
Extra: 013261d30c1181af1ced492e13b9ce40e1897b9c684a0bd0e87de87e66d2dc5f1f02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc47828f44d42949126cbbcb192ffc2919c12e80ae45015e859b083d94c60e45 0.600000000000 1402221 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": 944005, "vin": [ { "gen": { "height": 943995 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc47828f44d42949126cbbcb192ffc2919c12e80ae45015e859b083d94c60e45" } } ], "extra": [ 1, 50, 97, 211, 12, 17, 129, 175, 28, 237, 73, 46, 19, 185, 206, 64, 225, 137, 123, 156, 104, 74, 11, 208, 232, 125, 232, 126, 102, 210, 220, 95, 31, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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