Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa7871fb9bfb257ca6550ed50dbd1d40a8eef41af88fb313fb2315326686f075

Tx prefix hash: 03e20606c07358b91283f3340ab36def32cae5c128dd4996677bb5383e93be96
Tx public key: a9e79bc2ae894c57932d6c29aee475f0bb3645722614a2d8f0049977b81416c3
Timestamp: 1712528661 Timestamp [UCT]: 2024-04-07 22:24:21 Age [y:d:h:m:s]: 00:355:14:15:55
Block: 995578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254262 RingCT/type: yes/0
Extra: 01a9e79bc2ae894c57932d6c29aee475f0bb3645722614a2d8f0049977b81416c302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e82e669b0c25e1889c2e098e23d04529bfd1dc73c86e81611797e11ffad5658d 0.600000000000 1455988 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": 995588, "vin": [ { "gen": { "height": 995578 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e82e669b0c25e1889c2e098e23d04529bfd1dc73c86e81611797e11ffad5658d" } } ], "extra": [ 1, 169, 231, 155, 194, 174, 137, 76, 87, 147, 45, 108, 41, 174, 228, 117, 240, 187, 54, 69, 114, 38, 20, 162, 216, 240, 4, 153, 119, 184, 20, 22, 195, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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