Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92eea7c1c74935e88a758e340a94404e63f02ae5adc834224c0723bd13f20b57

Tx prefix hash: 5ce6d315ba242b70d5727d4381d647d9b3348196a3544c8c52c13bcec0dc84dc
Tx public key: 653e2b1b992e34188e32ffe960cb26896396d8707f272dd03c2ff0f32c448979
Timestamp: 1657217264 Timestamp [UCT]: 2022-07-07 18:07:44 Age [y:d:h:m:s]: 02:257:05:07:39
Block: 538770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 704970 RingCT/type: yes/0
Extra: 01653e2b1b992e34188e32ffe960cb26896396d8707f272dd03c2ff0f32c4489790211000000015eb576c5000000000000000000

1 output(s) for total of 10.065410341000 dcy

stealth address amount amount idx
00: 12954da684a4fe96e7b5d2ffb518c492411632a5de18ce963bc80dc8d2d984c7 10.065410341000 968809 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": 538780, "vin": [ { "gen": { "height": 538770 } } ], "vout": [ { "amount": 10065410341, "target": { "key": "12954da684a4fe96e7b5d2ffb518c492411632a5de18ce963bc80dc8d2d984c7" } } ], "extra": [ 1, 101, 62, 43, 27, 153, 46, 52, 24, 142, 50, 255, 233, 96, 203, 38, 137, 99, 150, 216, 112, 127, 39, 45, 208, 60, 47, 240, 243, 44, 68, 137, 121, 2, 17, 0, 0, 0, 1, 94, 181, 118, 197, 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