Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a50ecc3a019cec60b74d12b6bfc3ca5cc299c4823c56ec5fa9f6725ab91ded2

Tx prefix hash: fa0675bcb9d2b44b50eac94d242c9579c65a9bc51aeeb087849875a663d384f4
Tx public key: 7cf0353c346bd851a9c7eee7cfca5296ae5bb481d69faee59b8d78c2b20334bd
Timestamp: 1733659367 Timestamp [UCT]: 2024-12-08 12:02:47 Age [y:d:h:m:s]: 00:116:22:04:13
Block: 1170702 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83357 RingCT/type: yes/0
Extra: 017cf0353c346bd851a9c7eee7cfca5296ae5bb481d69faee59b8d78c2b20334bd021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73848a19bc299a04fdc5024e705f4b061278a4313e19ddfd9cbe92a6f6372acd 0.600000000000 1656433 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": 1170712, "vin": [ { "gen": { "height": 1170702 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73848a19bc299a04fdc5024e705f4b061278a4313e19ddfd9cbe92a6f6372acd" } } ], "extra": [ 1, 124, 240, 53, 60, 52, 107, 216, 81, 169, 199, 238, 231, 207, 202, 82, 150, 174, 91, 180, 129, 214, 159, 174, 229, 155, 141, 120, 194, 178, 3, 52, 189, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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