Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a22c254bf469c21481401fdd5a8de53cca476e35b2fb662ff351881a028d592

Tx prefix hash: 160ce25ea710d5113b432242640f1ceb0a71f23b16bcafa7d7d04071ca191531
Tx public key: 9b408e95765927080a8826bc08e30717c68d1c6882f88ce7c2cb1ae0348cd0a0
Timestamp: 1722086433 Timestamp [UCT]: 2024-07-27 13:20:33 Age [y:d:h:m:s]: 00:239:20:30:04
Block: 1074849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171327 RingCT/type: yes/0
Extra: 019b408e95765927080a8826bc08e30717c68d1c6882f88ce7c2cb1ae0348cd0a002110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fcef437a3fbe4e50b4a64862b1b37d244b6126adff64c33820d7c0e72c244fd2 0.600000000000 1547368 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": 1074859, "vin": [ { "gen": { "height": 1074849 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fcef437a3fbe4e50b4a64862b1b37d244b6126adff64c33820d7c0e72c244fd2" } } ], "extra": [ 1, 155, 64, 142, 149, 118, 89, 39, 8, 10, 136, 38, 188, 8, 227, 7, 23, 198, 141, 28, 104, 130, 248, 140, 231, 194, 203, 26, 224, 52, 140, 208, 160, 2, 17, 0, 0, 0, 11, 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