Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed45cc7517f2a7618f9cc1e943213f394a46a3fdf78a9fe6b4b4645d381050d7

Tx prefix hash: dd6ae0cf2b18b731e473df2afcc4f55c7c8a6eb5198bb8db8bcfb8476d7d2b4c
Tx public key: 0f9ef4f9221dfd89e6ec060c2681d5db7b4ca137f418468bab174168801550e4
Timestamp: 1719941990 Timestamp [UCT]: 2024-07-02 17:39:50 Age [y:d:h:m:s]: 01:172:14:13:30
Block: 1057074 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381934 RingCT/type: yes/0
Extra: 010f9ef4f9221dfd89e6ec060c2681d5db7b4ca137f418468bab174168801550e40211000000018fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b13bac967b38a0c9113cbc74447414274562910e6bec2f07c9160180267e00ba 0.600000000000 1527503 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": 1057084, "vin": [ { "gen": { "height": 1057074 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b13bac967b38a0c9113cbc74447414274562910e6bec2f07c9160180267e00ba" } } ], "extra": [ 1, 15, 158, 244, 249, 34, 29, 253, 137, 230, 236, 6, 12, 38, 129, 213, 219, 123, 76, 161, 55, 244, 24, 70, 139, 171, 23, 65, 104, 128, 21, 80, 228, 2, 17, 0, 0, 0, 1, 143, 218, 155, 45, 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