Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00830a7fc32b8caa1a9c4da8b7e96eaee2988deb2ab54ccb7f14d23020e171e6

Tx prefix hash: ce43d0b8e0167ef418cef18ba12aceb6f1aff14f6aefcebba68624b26c8efeda
Tx public key: a5d3eb5678b6133b76bb3d7594dc38cc99c4689df66841de25bdce2cc9847a1f
Timestamp: 1719103057 Timestamp [UCT]: 2024-06-23 00:37:37 Age [y:d:h:m:s]: 01:136:21:43:52
Block: 1050097 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356408 RingCT/type: yes/0
Extra: 01a5d3eb5678b6133b76bb3d7594dc38cc99c4689df66841de25bdce2cc9847a1f02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 365917e04e2cb240e84bd86e054f39bde6fca0c7f87d8bd4a425870247ac3eb2 0.600000000000 1520254 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": 1050107, "vin": [ { "gen": { "height": 1050097 } } ], "vout": [ { "amount": 600000000, "target": { "key": "365917e04e2cb240e84bd86e054f39bde6fca0c7f87d8bd4a425870247ac3eb2" } } ], "extra": [ 1, 165, 211, 235, 86, 120, 182, 19, 59, 118, 187, 61, 117, 148, 220, 56, 204, 153, 196, 104, 157, 246, 104, 65, 222, 37, 189, 206, 44, 201, 132, 122, 31, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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