Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d95c50dcfddfdc6501036028b789964438670015716cf4a2710322f8d66848d7

Tx prefix hash: 8bf3927dd6d73057564550696fe92399b7e3ec24dcb84363f01a08ae002e2e54
Tx public key: b50dd87063c69d4de52279d5f476bd9f27d51ba7b20f0b4fb913101f86c29184
Timestamp: 1707702645 Timestamp [UCT]: 2024-02-12 01:50:45 Age [y:d:h:m:s]: 00:314:19:26:22
Block: 955592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225424 RingCT/type: yes/0
Extra: 01b50dd87063c69d4de52279d5f476bd9f27d51ba7b20f0b4fb913101f86c291840211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ebeebea7a6a61b9b881f4dfd1348373a994b9ecbb212f2c71cfa9f4d4c26cd17 0.600000000000 1414888 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": 955602, "vin": [ { "gen": { "height": 955592 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ebeebea7a6a61b9b881f4dfd1348373a994b9ecbb212f2c71cfa9f4d4c26cd17" } } ], "extra": [ 1, 181, 13, 216, 112, 99, 198, 157, 77, 229, 34, 121, 213, 244, 118, 189, 159, 39, 213, 27, 167, 178, 15, 11, 79, 185, 19, 16, 31, 134, 194, 145, 132, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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