Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af2e4c367b59986876512bb69d6e6079b6278e31553c33463472b3f5d603a066

Tx prefix hash: 7d71715361cf1048637d7479cbd4ba7dbde4b13e1dee1f32db518752b3f6b831
Tx public key: 1dbaa21dfb31f44603b30e9bea328b6c621737b86f62c842790680f24d35f7f5
Timestamp: 1706939283 Timestamp [UCT]: 2024-02-03 05:48:03 Age [y:d:h:m:s]: 00:347:18:07:16
Block: 949258 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248964 RingCT/type: yes/0
Extra: 011dbaa21dfb31f44603b30e9bea328b6c621737b86f62c842790680f24d35f7f50211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dee411b9f13ce6f63097d1ce269e0c159c00c240a3499ecf4d76bfa2f4ca1bab 0.600000000000 1407780 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": 949268, "vin": [ { "gen": { "height": 949258 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dee411b9f13ce6f63097d1ce269e0c159c00c240a3499ecf4d76bfa2f4ca1bab" } } ], "extra": [ 1, 29, 186, 162, 29, 251, 49, 244, 70, 3, 179, 14, 155, 234, 50, 139, 108, 98, 23, 55, 184, 111, 98, 200, 66, 121, 6, 128, 242, 77, 53, 247, 245, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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