Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50c26106b339c4b2d63db6ba79c9c0b90a5c9736cfbd90ae024fe2444b66a117

Tx prefix hash: 066d2600781230f5cdcfdaa1f8ba4b32160621db0b2c4b6fea15e484855c731f
Tx public key: a92d4a6f37f0d9226c080aa7f732fddf4c1421aa6fc979224a63f2f05bec7afa
Timestamp: 1722123928 Timestamp [UCT]: 2024-07-27 23:45:28 Age [y:d:h:m:s]: 00:303:17:16:06
Block: 1075161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217014 RingCT/type: yes/0
Extra: 01a92d4a6f37f0d9226c080aa7f732fddf4c1421aa6fc979224a63f2f05bec7afa021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3a792c54a479a908ea299e527be3ac3a7b052d127e953e97f58d09ea8de95ec 0.600000000000 1547684 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": 1075171, "vin": [ { "gen": { "height": 1075161 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3a792c54a479a908ea299e527be3ac3a7b052d127e953e97f58d09ea8de95ec" } } ], "extra": [ 1, 169, 45, 74, 111, 55, 240, 217, 34, 108, 8, 10, 167, 247, 50, 253, 223, 76, 20, 33, 170, 111, 201, 121, 34, 74, 99, 242, 240, 91, 236, 122, 250, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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