Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04e6aee500d287a89893bca4f9b34e02f871a163033caa62a81a2bc20cb9487e

Tx prefix hash: 043eb895dfe71dc213ad77d22eda6e206e4a607e8694e6380a309d33b223bbcb
Tx public key: 09a302483112207f6755c5e610f2a797892ed107d1d5c13c8d3fa22721c818df
Timestamp: 1649668058 Timestamp [UCT]: 2022-04-11 09:07:38 Age [y:d:h:m:s]: 02:218:19:33:05
Block: 477861 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 676144 RingCT/type: yes/0
Extra: 0109a302483112207f6755c5e610f2a797892ed107d1d5c13c8d3fa22721c818df021100000007d3fcec30000000000000000000

1 output(s) for total of 16.019478556000 dcy

stealth address amount amount idx
00: 1ded69b856e3b30915489a26ccf504311eed3731956abbd3988941ef0f6dbea5 16.019478556000 898566 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": 477871, "vin": [ { "gen": { "height": 477861 } } ], "vout": [ { "amount": 16019478556, "target": { "key": "1ded69b856e3b30915489a26ccf504311eed3731956abbd3988941ef0f6dbea5" } } ], "extra": [ 1, 9, 163, 2, 72, 49, 18, 32, 127, 103, 85, 197, 230, 16, 242, 167, 151, 137, 46, 209, 7, 209, 213, 193, 60, 141, 63, 162, 39, 33, 200, 24, 223, 2, 17, 0, 0, 0, 7, 211, 252, 236, 48, 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