Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cee43acb18d91d7d14522b0c2f31ccee5f7e83d963739fd1c1025af0d55fe47

Tx prefix hash: 87f5bf4994708fe6e59279b098f9ed1b2c86e6f668879e66675cbef335cea20e
Tx public key: 722f87ab211de2b276edab6126354a8d293ae697ce12e2ce6d775f527b662749
Timestamp: 1681630211 Timestamp [UCT]: 2023-04-16 07:30:11 Age [y:d:h:m:s]: 01:360:13:03:27
Block: 739687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 518967 RingCT/type: yes/0
Extra: 01722f87ab211de2b276edab6126354a8d293ae697ce12e2ce6d775f527b6627490211000000015029cbac000000000000000000

1 output(s) for total of 2.173372203000 dcy

stealth address amount amount idx
00: 8fca0cfb52380275e7d90cbf6e7792cfce570ab95fea0ec1508fdf261d05ab0a 2.173372203000 1186550 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": 739697, "vin": [ { "gen": { "height": 739687 } } ], "vout": [ { "amount": 2173372203, "target": { "key": "8fca0cfb52380275e7d90cbf6e7792cfce570ab95fea0ec1508fdf261d05ab0a" } } ], "extra": [ 1, 114, 47, 135, 171, 33, 29, 226, 178, 118, 237, 171, 97, 38, 53, 74, 141, 41, 58, 230, 151, 206, 18, 226, 206, 109, 119, 95, 82, 123, 102, 39, 73, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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