Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc5c50810f7eba8d6ccda749dc7e2e0dff568359a1062daed6718727c7c58290

Tx prefix hash: afda6db117dcc5f1f1fa749f2e8be80308d6ab9357e040928183fe537680527f
Tx public key: c0fca608e7e92eb2f298dcb9a4bdbaefd2e42aecceb6726c8314871f227e913d
Timestamp: 1710344727 Timestamp [UCT]: 2024-03-13 15:45:27 Age [y:d:h:m:s]: 01:239:15:52:18
Block: 977528 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 429975 RingCT/type: yes/0
Extra: 01c0fca608e7e92eb2f298dcb9a4bdbaefd2e42aecceb6726c8314871f227e913d02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1eb78c77b33901b0cf8638dbe196f18364ce381250a9517ca503ed9b88236c29 0.600000000000 1437531 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": 977538, "vin": [ { "gen": { "height": 977528 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1eb78c77b33901b0cf8638dbe196f18364ce381250a9517ca503ed9b88236c29" } } ], "extra": [ 1, 192, 252, 166, 8, 231, 233, 46, 178, 242, 152, 220, 185, 164, 189, 186, 239, 210, 228, 42, 236, 206, 182, 114, 108, 131, 20, 135, 31, 34, 126, 145, 61, 2, 17, 0, 0, 0, 5, 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