Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3b3d58ea064e80757c600d7f17bae5722cf95d72142ffd938d9265b17f8b2f7

Tx prefix hash: 5082df1a46067c180cbbd9bd5ab9629ff494cf398005416328252ae64309ad5b
Tx public key: 2c7a412a32fe10c90c47a51edd6cb87174461b51e43d1f508119541d88755a35
Timestamp: 1703962546 Timestamp [UCT]: 2023-12-30 18:55:46 Age [y:d:h:m:s]: 01:058:19:57:30
Block: 924586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303135 RingCT/type: yes/0
Extra: 012c7a412a32fe10c90c47a51edd6cb87174461b51e43d1f508119541d88755a350211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600060000000 dcy

stealth address amount amount idx
00: 7689610a5a1adc07fa32c94acd44b271c6faaa6ec1d17cf291d7e91a59582c78 0.600060000000 1382340 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": 924596, "vin": [ { "gen": { "height": 924586 } } ], "vout": [ { "amount": 600060000, "target": { "key": "7689610a5a1adc07fa32c94acd44b271c6faaa6ec1d17cf291d7e91a59582c78" } } ], "extra": [ 1, 44, 122, 65, 42, 50, 254, 16, 201, 12, 71, 165, 30, 221, 108, 184, 113, 116, 70, 27, 81, 228, 61, 31, 80, 129, 25, 84, 29, 136, 117, 90, 53, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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