Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56cdfc9fad5d1698fffb501494f8bcc62bb365ddac6f7f2fc4e9ff2e1ac318ad

Tx prefix hash: d4b09e73cb667e503af9e26b579cce4cdf122abd73bba611e6e1d77f70f08f44
Tx public key: 6bc2dd9f5476366f6e2402a6cb37d9d3960de1e0344e8f9844f029d7457b0870
Timestamp: 1635288042 Timestamp [UCT]: 2021-10-26 22:40:42 Age [y:d:h:m:s]: 03:090:08:39:33
Block: 361142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 842988 RingCT/type: yes/0
Extra: 016bc2dd9f5476366f6e2402a6cb37d9d3960de1e0344e8f9844f029d7457b0870021100000001a272b9cb000000000000000000

1 output(s) for total of 39.028965864000 dcy

stealth address amount amount idx
00: 7cd597112a2ffb06ac1cdb52bc8432d2b4f212be6eb2d63519edf77ce4d70c2b 39.028965864000 734849 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": 361152, "vin": [ { "gen": { "height": 361142 } } ], "vout": [ { "amount": 39028965864, "target": { "key": "7cd597112a2ffb06ac1cdb52bc8432d2b4f212be6eb2d63519edf77ce4d70c2b" } } ], "extra": [ 1, 107, 194, 221, 159, 84, 118, 54, 111, 110, 36, 2, 166, 203, 55, 217, 211, 150, 13, 225, 224, 52, 78, 143, 152, 68, 240, 41, 215, 69, 123, 8, 112, 2, 17, 0, 0, 0, 1, 162, 114, 185, 203, 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