Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bcf79dc7527f0eb27268af0f8cf9268cb03b1bd5c3945a08609c2ca1f446321

Tx prefix hash: feededf6bae7ce1de3b2f5a7003db26c4ba234ff342e8d8968628476832014a4
Tx public key: f349083884cc2b5743dc581485a4a9df6968e8a3051b037f0bcb4b4780411b98
Timestamp: 1739906420 Timestamp [UCT]: 2025-02-18 19:20:20 Age [y:d:h:m:s]: 00:081:21:51:43
Block: 1222121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58608 RingCT/type: yes/0
Extra: 01f349083884cc2b5743dc581485a4a9df6968e8a3051b037f0bcb4b4780411b980211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25cabaa6da6b612eed8c3c7ec98c3547714d424798125755fc9d46d4ecf8d3c5 0.600000000000 1708968 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": 1222131, "vin": [ { "gen": { "height": 1222121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25cabaa6da6b612eed8c3c7ec98c3547714d424798125755fc9d46d4ecf8d3c5" } } ], "extra": [ 1, 243, 73, 8, 56, 132, 204, 43, 87, 67, 220, 88, 20, 133, 164, 169, 223, 105, 104, 232, 163, 5, 27, 3, 127, 11, 203, 75, 71, 128, 65, 27, 152, 2, 17, 0, 0, 0, 1, 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