Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fca60913dad8b8c7686c806d5c65a0f3b9eb40ff8490baa2807c42dd0f2ec777

Tx prefix hash: 77edcc6e707f7435167f3887f969738a5ab9aa89200d2aa5f6246bc85f748420
Tx public key: 488410f79d6c584d2b3ae0715a2c9a257ca356acccef6aee4335f608ba9156c4
Timestamp: 1722788579 Timestamp [UCT]: 2024-08-04 16:22:59 Age [y:d:h:m:s]: 00:224:19:59:44
Block: 1080666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160600 RingCT/type: yes/0
Extra: 01488410f79d6c584d2b3ae0715a2c9a257ca356acccef6aee4335f608ba9156c4021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf7323d41b2cd9de0c87c33a56c434d829d0f5fd78f242e8a8684bdc79893e81 0.600000000000 1554115 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": 1080676, "vin": [ { "gen": { "height": 1080666 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf7323d41b2cd9de0c87c33a56c434d829d0f5fd78f242e8a8684bdc79893e81" } } ], "extra": [ 1, 72, 132, 16, 247, 157, 108, 88, 77, 43, 58, 224, 113, 90, 44, 154, 37, 124, 163, 86, 172, 204, 239, 106, 238, 67, 53, 246, 8, 186, 145, 86, 196, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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