Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8cbb6688a2f49f7ee39efb4f2da95a4112ef07e36d3d4dfbe6e72f18495f4c33

Tx prefix hash: 63f2037c81f9d6fb13bd89c2c74741bba9386431d2cd06658584492dae2242f9
Tx public key: 00c049d7b220912f2794d76203adba5e8d335327757b83d7fe20d3ecfee40134
Timestamp: 1735286972 Timestamp [UCT]: 2024-12-27 08:09:32 Age [y:d:h:m:s]: 00:095:12:01:41
Block: 1184158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68039 RingCT/type: yes/0
Extra: 0100c049d7b220912f2794d76203adba5e8d335327757b83d7fe20d3ecfee401340211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af826c6d05b3a2e3e24ae8cc3c29440d2e0ae43f8f858107da19d210e11f397a 0.600000000000 1670611 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": 1184168, "vin": [ { "gen": { "height": 1184158 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af826c6d05b3a2e3e24ae8cc3c29440d2e0ae43f8f858107da19d210e11f397a" } } ], "extra": [ 1, 0, 192, 73, 215, 178, 32, 145, 47, 39, 148, 215, 98, 3, 173, 186, 94, 141, 51, 83, 39, 117, 123, 131, 215, 254, 32, 211, 236, 254, 228, 1, 52, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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