Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74769c4799f526f5f674d32a32a6fbd5015fd95318921d718cc6c314a1e2d69f

Tx prefix hash: 49677a82e854868e7e7c7ea6ea2043cdb22fd07aff9ae19e0c220b86f44fb057
Tx public key: d598e53106ecb497dae6f4fd70a9be3a5ea64bdd3142e87ba6e54975d19e7361
Timestamp: 1636207977 Timestamp [UCT]: 2021-11-06 14:12:57 Age [y:d:h:m:s]: 03:174:17:15:50
Block: 368626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 903242 RingCT/type: yes/0
Extra: 01d598e53106ecb497dae6f4fd70a9be3a5ea64bdd3142e87ba6e54975d19e736102110000002b4f792ffd000000000000000000

1 output(s) for total of 36.862894589000 dcy

stealth address amount amount idx
00: 3736e8b31951359f1a6dcb1961f9d48c2bdaaf1beb4007ab14b43ad3c5be3a70 36.862894589000 747636 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": 368636, "vin": [ { "gen": { "height": 368626 } } ], "vout": [ { "amount": 36862894589, "target": { "key": "3736e8b31951359f1a6dcb1961f9d48c2bdaaf1beb4007ab14b43ad3c5be3a70" } } ], "extra": [ 1, 213, 152, 229, 49, 6, 236, 180, 151, 218, 230, 244, 253, 112, 169, 190, 58, 94, 166, 75, 221, 49, 66, 232, 123, 166, 229, 73, 117, 209, 158, 115, 97, 2, 17, 0, 0, 0, 43, 79, 121, 47, 253, 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