Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35cdacce45eb929045488c4c54ba5055a6025075e6ade5417afd72c847669b5c

Tx prefix hash: 3aa360f71e16ae74b4333d2f8f3b5716460df5d98fcdb02e9801f02bfa3732e3
Tx public key: a25a3fb4ae5dcb6a7a18e8eb49a6d57eac37c1b72c4986ecbaa1ad4b19ddd647
Timestamp: 1657278463 Timestamp [UCT]: 2022-07-08 11:07:43 Age [y:d:h:m:s]: 02:263:14:39:00
Block: 539280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 709521 RingCT/type: yes/0
Extra: 01a25a3fb4ae5dcb6a7a18e8eb49a6d57eac37c1b72c4986ecbaa1ad4b19ddd647021100000002bf7ee4e7000000000000000000

1 output(s) for total of 10.026321864000 dcy

stealth address amount amount idx
00: 0157e795eaeed999c6e11fd5ad4bec55388c599061198f66322dfe902c3c34b8 10.026321864000 969365 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": 539290, "vin": [ { "gen": { "height": 539280 } } ], "vout": [ { "amount": 10026321864, "target": { "key": "0157e795eaeed999c6e11fd5ad4bec55388c599061198f66322dfe902c3c34b8" } } ], "extra": [ 1, 162, 90, 63, 180, 174, 93, 203, 106, 122, 24, 232, 235, 73, 166, 213, 126, 172, 55, 193, 183, 44, 73, 134, 236, 186, 161, 173, 75, 25, 221, 214, 71, 2, 17, 0, 0, 0, 2, 191, 126, 228, 231, 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