Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05a4d7106c9f11b9f73c446673c4773c36cd3e724e7183f5b63a5c53f3665029

Tx prefix hash: 3fc52fe6c3ee9bfad8b6ed44c5ee309cae02d139d5a251b7d16d3f899602924f
Tx public key: 0f65803ef221825c310a6377ca0ba492ff1f3b566b6dd4fd7014fe4f77d57886
Timestamp: 1732861511 Timestamp [UCT]: 2024-11-29 06:25:11 Age [y:d:h:m:s]: 00:200:08:46:26
Block: 1164084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142950 RingCT/type: yes/0
Extra: 010f65803ef221825c310a6377ca0ba492ff1f3b566b6dd4fd7014fe4f77d578860211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68fd3d1b8cd42596df8f994b64398eee9ba7829da1317a0dd9cba49ed27ce7b3 0.600000000000 1649757 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": 1164094, "vin": [ { "gen": { "height": 1164084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68fd3d1b8cd42596df8f994b64398eee9ba7829da1317a0dd9cba49ed27ce7b3" } } ], "extra": [ 1, 15, 101, 128, 62, 242, 33, 130, 92, 49, 10, 99, 119, 202, 11, 164, 146, 255, 31, 59, 86, 107, 109, 212, 253, 112, 20, 254, 79, 119, 213, 120, 134, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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