Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6bd6934746f6d4091bb0a8653345a35540c0a48b86fbc52dc3b2525d4f5e721

Tx prefix hash: 50927861492484a5129a221f884d3ca595eac7cd2da291f8617a71926b29b60e
Tx public key: e12272e6e9c0295988a2bef8f12e37245f0fd36a640e9a92df6165d055f5eaba
Timestamp: 1697043545 Timestamp [UCT]: 2023-10-11 16:59:05 Age [y:d:h:m:s]: 02:029:23:20:45
Block: 867437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 541046 RingCT/type: yes/0
Extra: 01e12272e6e9c0295988a2bef8f12e37245f0fd36a640e9a92df6165d055f5eaba02110000000333af99f4000000000000000000

1 output(s) for total of 0.820013797000 dcy

stealth address amount amount idx
00: f0b4351f74e1bbfaf1dd994db08476b6e7da44a5a7ecbba72217258684fc1f10 0.820013797000 1322123 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": 867447, "vin": [ { "gen": { "height": 867437 } } ], "vout": [ { "amount": 820013797, "target": { "key": "f0b4351f74e1bbfaf1dd994db08476b6e7da44a5a7ecbba72217258684fc1f10" } } ], "extra": [ 1, 225, 34, 114, 230, 233, 192, 41, 89, 136, 162, 190, 248, 241, 46, 55, 36, 95, 15, 211, 106, 100, 14, 154, 146, 223, 97, 101, 208, 85, 245, 234, 186, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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