Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c0d618022441c505ec0f60bd677c35b65fac15005b20ef1922ecb581975dd74

Tx prefix hash: 4b85dfbd3616d016243b2244538c97077ac7a1cb2ec3341db7b36380a79bdd56
Tx public key: fbc36f7669505c3de9dfa3b6c0581238d865b5c4a0d3a34a50963890a5cea554
Timestamp: 1713428766 Timestamp [UCT]: 2024-04-18 08:26:06 Age [y:d:h:m:s]: 00:356:19:20:18
Block: 1003060 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255100 RingCT/type: yes/0
Extra: 01fbc36f7669505c3de9dfa3b6c0581238d865b5c4a0d3a34a50963890a5cea5540211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a743b0e80afbb45dd01b4945b7c81b534a52da079c95ef38d614cb5fc3cb77f 0.600000000000 1463590 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": 1003070, "vin": [ { "gen": { "height": 1003060 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a743b0e80afbb45dd01b4945b7c81b534a52da079c95ef38d614cb5fc3cb77f" } } ], "extra": [ 1, 251, 195, 111, 118, 105, 80, 92, 61, 233, 223, 163, 182, 192, 88, 18, 56, 216, 101, 181, 196, 160, 211, 163, 74, 80, 150, 56, 144, 165, 206, 165, 84, 2, 17, 0, 0, 0, 5, 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