Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ce8efe558f045f3f67b38f656a0100dc2849ad4f60f4f22dbe35c7d36d82c55

Tx prefix hash: 504b9beb10dc2f7f69d56181d85341b46e07454849fe8f2c53297000fa212919
Tx public key: 07c83b3ea06fd2fea9daa9d7556ecb90a31c6095c4796119b0e17630cfc036ec
Timestamp: 1576643566 Timestamp [UCT]: 2019-12-18 04:32:46 Age [y:d:h:m:s]: 04:335:13:54:42
Block: 28287 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1126840 RingCT/type: yes/0
Extra: 0107c83b3ea06fd2fea9daa9d7556ecb90a31c6095c4796119b0e17630cfc036ec0211000000139159db1e000000000000000000

1 output(s) for total of 494.622981877000 dcy

stealth address amount amount idx
00: 9aac7c3f582c5cfe66a2e7b29261d26aa8c5e7f69c8e9fba3adc636c8d6b0e77 494.622981877000 46819 of 0

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": 28297, "vin": [ { "gen": { "height": 28287 } } ], "vout": [ { "amount": 494622981877, "target": { "key": "9aac7c3f582c5cfe66a2e7b29261d26aa8c5e7f69c8e9fba3adc636c8d6b0e77" } } ], "extra": [ 1, 7, 200, 59, 62, 160, 111, 210, 254, 169, 218, 169, 215, 85, 110, 203, 144, 163, 28, 96, 149, 196, 121, 97, 25, 176, 225, 118, 48, 207, 192, 54, 236, 2, 17, 0, 0, 0, 19, 145, 89, 219, 30, 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