Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08aa60cdee0189eb1e70a185f04439b88b6873b758bebf77a5908f5cb1d37f67

Tx prefix hash: bba8c5dec8d6e7613c55941e4924c7e2f4596d6c9e76727c6859e738cc60f9ff
Tx public key: ad0c0d3d5cc9248a5110cb037a48196ef8bc3b3f8f928a2ac8b383e356dbb4bf
Timestamp: 1712792471 Timestamp [UCT]: 2024-04-10 23:41:11 Age [y:d:h:m:s]: 01:207:00:24:23
Block: 997777 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406628 RingCT/type: yes/0
Extra: 01ad0c0d3d5cc9248a5110cb037a48196ef8bc3b3f8f928a2ac8b383e356dbb4bf02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 124362dc37bc0e4b38676c0a3b7f813bf4a59b7b06eab4a0da45bde01d971227 0.600000000000 1458211 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": 997787, "vin": [ { "gen": { "height": 997777 } } ], "vout": [ { "amount": 600000000, "target": { "key": "124362dc37bc0e4b38676c0a3b7f813bf4a59b7b06eab4a0da45bde01d971227" } } ], "extra": [ 1, 173, 12, 13, 61, 92, 201, 36, 138, 81, 16, 203, 3, 122, 72, 25, 110, 248, 188, 59, 63, 143, 146, 138, 42, 200, 179, 131, 227, 86, 219, 180, 191, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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