Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca05b548c2c4d15cb5133fbde03033c9d20e7b97d184f077f0bc80af6e30008f

Tx prefix hash: 06ae555006dc147446f124fab3cc44adcd8a7b2363062088fec946e7f5b197d3
Tx public key: c35627702fb649013acd6253f4d337e774a014693f4934ef2aa0aca4c6e46b80
Timestamp: 1581925987 Timestamp [UCT]: 2020-02-17 07:53:07 Age [y:d:h:m:s]: 05:235:02:37:40
Block: 66540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1318840 RingCT/type: yes/0
Extra: 01c35627702fb649013acd6253f4d337e774a014693f4934ef2aa0aca4c6e46b800211000000024943cd9f000000000000000000

1 output(s) for total of 369.424901911000 dcy

stealth address amount amount idx
00: 39856b6ffd9ee9f2424c49082ccacf7780305b0eed747575be1587ead8e009a5 369.424901911000 122587 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": 66550, "vin": [ { "gen": { "height": 66540 } } ], "vout": [ { "amount": 369424901911, "target": { "key": "39856b6ffd9ee9f2424c49082ccacf7780305b0eed747575be1587ead8e009a5" } } ], "extra": [ 1, 195, 86, 39, 112, 47, 182, 73, 1, 58, 205, 98, 83, 244, 211, 55, 231, 116, 160, 20, 105, 63, 73, 52, 239, 42, 160, 172, 164, 198, 228, 107, 128, 2, 17, 0, 0, 0, 2, 73, 67, 205, 159, 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