Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ae1c3ec91f2842519642e057f1e2642cc5b3368b368cbbbb69a8c73c7ec4921

Tx prefix hash: 6c041038285d94ebdea35e4cd6442c37d6c612d11dea86b11678bb8f44609d18
Tx public key: 68700d0de5284ea9e82183f0720dafe6a1f2e1e31a1e36471bec1e4628fbc222
Timestamp: 1719860109 Timestamp [UCT]: 2024-07-01 18:55:09 Age [y:d:h:m:s]: 00:205:09:57:04
Block: 1056391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146949 RingCT/type: yes/0
Extra: 0168700d0de5284ea9e82183f0720dafe6a1f2e1e31a1e36471bec1e4628fbc2220211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 69edacfbcb69387c5087c71077a98a616110df2cbdfa213c2ace8d3834efc735 0.600000000000 1526804 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": 1056401, "vin": [ { "gen": { "height": 1056391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "69edacfbcb69387c5087c71077a98a616110df2cbdfa213c2ace8d3834efc735" } } ], "extra": [ 1, 104, 112, 13, 13, 229, 40, 78, 169, 232, 33, 131, 240, 114, 13, 175, 230, 161, 242, 225, 227, 26, 30, 54, 71, 27, 236, 30, 70, 40, 251, 194, 34, 2, 17, 0, 0, 0, 2, 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