Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21bc8dc966b76f04651dbd90dd9656a06f2b066fc6479d6bbd1db56fb5c7dc31

Tx prefix hash: ac1da3d39a9fe253630df9047f7a64098cfe883711032b923728fa901e09341e
Tx public key: 5612e5ec974881c77737645956cb6464c567f02116181a3a3a6a11fe86f3fb27
Timestamp: 1706990229 Timestamp [UCT]: 2024-02-03 19:57:09 Age [y:d:h:m:s]: 01:025:17:34:39
Block: 949680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279427 RingCT/type: yes/0
Extra: 015612e5ec974881c77737645956cb6464c567f02116181a3a3a6a11fe86f3fb270211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a86d8139fcad210a4e16eae661b113f2384b2bfc7dab90c6dea811dfbe4adf2 0.600000000000 1408210 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": 949690, "vin": [ { "gen": { "height": 949680 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a86d8139fcad210a4e16eae661b113f2384b2bfc7dab90c6dea811dfbe4adf2" } } ], "extra": [ 1, 86, 18, 229, 236, 151, 72, 129, 199, 119, 55, 100, 89, 86, 203, 100, 100, 197, 103, 240, 33, 22, 24, 26, 58, 58, 106, 17, 254, 134, 243, 251, 39, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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