Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 815d6f6d200bce75234c4c1bfd2d023f74f2b33a8e20f2df63bb222e9e6f909c

Tx prefix hash: 8d1b0b6c952057a1d2eac63cb1d62c81695d53eeb0771ada9b8372b888349244
Tx public key: bd27ca708feaf360dbc8b80d41b7e10b1c0413dfd26f4e336188878562c17552
Timestamp: 1732554436 Timestamp [UCT]: 2024-11-25 17:07:16 Age [y:d:h:m:s]: 00:154:19:12:02
Block: 1161534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110477 RingCT/type: yes/0
Extra: 01bd27ca708feaf360dbc8b80d41b7e10b1c0413dfd26f4e336188878562c175520211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83ccf4d862058e006b08c347fba105240278986d081eebf2d4832dc9bcd70a3d 0.600000000000 1647189 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": 1161544, "vin": [ { "gen": { "height": 1161534 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83ccf4d862058e006b08c347fba105240278986d081eebf2d4832dc9bcd70a3d" } } ], "extra": [ 1, 189, 39, 202, 112, 143, 234, 243, 96, 219, 200, 184, 13, 65, 183, 225, 11, 28, 4, 19, 223, 210, 111, 78, 51, 97, 136, 135, 133, 98, 193, 117, 82, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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