Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0228104f92b73feb2b6b38d9d5e07a30ad73f72bd0bbeb9b632dbf07da793260

Tx prefix hash: 87a16f220029e9a660a9ccf10cd1b849ae6cf4db3c82a650b04bd0ca468386c5
Tx public key: 9f0fd2fdaf1a19ac0acfe7a861238010fa6af050f1da4fb6e7c81a472042c7ea
Timestamp: 1676242759 Timestamp [UCT]: 2023-02-12 22:59:19 Age [y:d:h:m:s]: 02:074:23:54:31
Block: 695678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 575214 RingCT/type: yes/0
Extra: 019f0fd2fdaf1a19ac0acfe7a861238010fa6af050f1da4fb6e7c81a472042c7ea0211000000015029cbac000000000000000000

1 output(s) for total of 3.040394344000 dcy

stealth address amount amount idx
00: 703e73179a7797d5b6f5afd2b7b3b6527a85b17c7ef36ece98be3e2d5e89b0b4 3.040394344000 1138635 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": 695688, "vin": [ { "gen": { "height": 695678 } } ], "vout": [ { "amount": 3040394344, "target": { "key": "703e73179a7797d5b6f5afd2b7b3b6527a85b17c7ef36ece98be3e2d5e89b0b4" } } ], "extra": [ 1, 159, 15, 210, 253, 175, 26, 25, 172, 10, 207, 231, 168, 97, 35, 128, 16, 250, 106, 240, 80, 241, 218, 79, 182, 231, 200, 26, 71, 32, 66, 199, 234, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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