Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6cfed222279efd5fdc7c02fb8107fbfdc9a8f288efc3dd6679c5a3b03ef7b97

Tx prefix hash: 131cfb0a828de6aef23b47693a72b3ad119f84038138ed815d536d0de67771f1
Tx public key: 04eb083508756cd986ea73faeeb1030de8e24dc35900537c67b0a40f65f23713
Timestamp: 1580617186 Timestamp [UCT]: 2020-02-02 04:19:46 Age [y:d:h:m:s]: 04:335:03:51:32
Block: 56855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1130886 RingCT/type: yes/0
Extra: 0104eb083508756cd986ea73faeeb1030de8e24dc35900537c67b0a40f65f23713021100000001bd0f9f9f000000000000000000

1 output(s) for total of 397.767107977000 dcy

stealth address amount amount idx
00: dc1fc3996cb3e9d44f456fc63b9cfbfbcbd5a22c6c17d474db08a5c078f9ce6a 397.767107977000 104842 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": 56865, "vin": [ { "gen": { "height": 56855 } } ], "vout": [ { "amount": 397767107977, "target": { "key": "dc1fc3996cb3e9d44f456fc63b9cfbfbcbd5a22c6c17d474db08a5c078f9ce6a" } } ], "extra": [ 1, 4, 235, 8, 53, 8, 117, 108, 217, 134, 234, 115, 250, 238, 177, 3, 13, 232, 226, 77, 195, 89, 0, 83, 124, 103, 176, 164, 15, 101, 242, 55, 19, 2, 17, 0, 0, 0, 1, 189, 15, 159, 159, 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