Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac7c0f424e044737d1a418f95c47aa7f000e0435aef6e5ca876e2b832d4330a8

Tx prefix hash: f0db950deccab12867ef64b8ad55b047a6693b61db61ad981c5f67af263b8741
Tx public key: fe202e74c3d521f05161ade86831f61d648f6a205104d6b71b8b5ee8f0845533
Timestamp: 1700346372 Timestamp [UCT]: 2023-11-18 22:26:12 Age [y:d:h:m:s]: 01:138:04:46:55
Block: 894611 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359947 RingCT/type: yes/0
Extra: 01fe202e74c3d521f05161ade86831f61d648f6a205104d6b71b8b5ee8f084553302110000000733af99f4000000000000000000

1 output(s) for total of 0.666472720000 dcy

stealth address amount amount idx
00: 0d5a02a01562320b1a7cae87a358b92d0fe450c320b99eb791d03440ca52d9a5 0.666472720000 1350814 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": 894621, "vin": [ { "gen": { "height": 894611 } } ], "vout": [ { "amount": 666472720, "target": { "key": "0d5a02a01562320b1a7cae87a358b92d0fe450c320b99eb791d03440ca52d9a5" } } ], "extra": [ 1, 254, 32, 46, 116, 195, 213, 33, 240, 81, 97, 173, 232, 104, 49, 246, 29, 100, 143, 106, 32, 81, 4, 214, 183, 27, 139, 94, 232, 240, 132, 85, 51, 2, 17, 0, 0, 0, 7, 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