Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11e3768da8f0b35da1177c549e7ab7611495758149f81ae650e3a32cea1d40f3

Tx prefix hash: 54714382fd2175e4a8ff8c16a64dff1042e53dba5b11acb1ee5a3ca8a96490f2
Tx public key: e4df636223a69dc74620e84f8380bbe24449b3013cce5fddcb573f2bc0524d39
Timestamp: 1724001919 Timestamp [UCT]: 2024-08-18 17:25:19 Age [y:d:h:m:s]: 00:226:09:38:17
Block: 1090739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161658 RingCT/type: yes/0
Extra: 01e4df636223a69dc74620e84f8380bbe24449b3013cce5fddcb573f2bc0524d3902110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23b0c9b131fbdc2dcafe0ab7b0fd70b9d564f3c9849ddfe806d35b58f7a0c5c4 0.600000000000 1565362 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": 1090749, "vin": [ { "gen": { "height": 1090739 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23b0c9b131fbdc2dcafe0ab7b0fd70b9d564f3c9849ddfe806d35b58f7a0c5c4" } } ], "extra": [ 1, 228, 223, 99, 98, 35, 166, 157, 199, 70, 32, 232, 79, 131, 128, 187, 226, 68, 73, 179, 1, 60, 206, 95, 221, 203, 87, 63, 43, 192, 82, 77, 57, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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