Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbc4877c55b144040ed4520cdee5c96a0a92602f9bef44b3c2d41b1c7639d5d4

Tx prefix hash: ff1e7268a260466e153fb1a14122974b73f22d008a647815a3823bc7743b2b96
Tx public key: 468402247d723feba97b9d6414ad08b638968527b646a30c9b1cd62ebf0e510d
Timestamp: 1734327266 Timestamp [UCT]: 2024-12-16 05:34:26 Age [y:d:h:m:s]: 00:105:01:24:35
Block: 1176245 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74845 RingCT/type: yes/0
Extra: 01468402247d723feba97b9d6414ad08b638968527b646a30c9b1cd62ebf0e510d021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 707b5fed9a243b96509e53c5f44fecd1d7bc03e3d89a41a39693a7028d4a43a6 0.600000000000 1662576 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": 1176255, "vin": [ { "gen": { "height": 1176245 } } ], "vout": [ { "amount": 600000000, "target": { "key": "707b5fed9a243b96509e53c5f44fecd1d7bc03e3d89a41a39693a7028d4a43a6" } } ], "extra": [ 1, 70, 132, 2, 36, 125, 114, 63, 235, 169, 123, 157, 100, 20, 173, 8, 182, 56, 150, 133, 39, 182, 70, 163, 12, 155, 28, 214, 46, 191, 14, 81, 13, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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