Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e07c9b3e5a884d57eba077aa96d45567054a3b9c07ac587b0dcacc862c0657e1

Tx prefix hash: fd3e74e00f82e0201bf3a3ca63e16043a01e2ccabd96b04d9ae456f19b8bc1db
Tx public key: 177cb6dc4f205a206c85a475c3fcfd5603795424c569e6b23ea8004fe76529ff
Timestamp: 1685510838 Timestamp [UCT]: 2023-05-31 05:27:18 Age [y:d:h:m:s]: 01:271:17:59:55
Block: 771880 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 455382 RingCT/type: yes/0
Extra: 01177cb6dc4f205a206c85a475c3fcfd5603795424c569e6b23ea8004fe76529ff021100000005e6d27f9c000000000000000000

1 output(s) for total of 1.699970200000 dcy

stealth address amount amount idx
00: 13cf7f5dca6ccf0f763c077f73642eea08370af0992182eddc576ad7138abcad 1.699970200000 1221261 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": 771890, "vin": [ { "gen": { "height": 771880 } } ], "vout": [ { "amount": 1699970200, "target": { "key": "13cf7f5dca6ccf0f763c077f73642eea08370af0992182eddc576ad7138abcad" } } ], "extra": [ 1, 23, 124, 182, 220, 79, 32, 90, 32, 108, 133, 164, 117, 195, 252, 253, 86, 3, 121, 84, 36, 197, 105, 230, 178, 62, 168, 0, 79, 231, 101, 41, 255, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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