Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb6c82f853d9b1b2406f34347ac7d0e86e2e574888f403737ab0a4ec84315bc7

Tx prefix hash: e0092f1b1e113737a67677d2348d21d6fc2347f9e44898fa2e46331693df2be6
Tx public key: d04c1c71bcfbb511056dd576a95079d80127e5c41209e0668136b40bd90e3040
Timestamp: 1730826472 Timestamp [UCT]: 2024-11-05 17:07:52 Age [y:d:h:m:s]: 00:145:12:12:45
Block: 1147219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103827 RingCT/type: yes/0
Extra: 01d04c1c71bcfbb511056dd576a95079d80127e5c41209e0668136b40bd90e30400211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f0a8721bb4a797b5ef98e4dab8977ba4c5b7dd6d91349b5fe6f4777b1e7cdff 0.600000000000 1631914 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": 1147229, "vin": [ { "gen": { "height": 1147219 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f0a8721bb4a797b5ef98e4dab8977ba4c5b7dd6d91349b5fe6f4777b1e7cdff" } } ], "extra": [ 1, 208, 76, 28, 113, 188, 251, 181, 17, 5, 109, 213, 118, 169, 80, 121, 216, 1, 39, 229, 196, 18, 9, 224, 102, 129, 54, 180, 11, 217, 14, 48, 64, 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