Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcd659b47b83f3c0e6fd97cadb5708e4a85cc9bd614e0d26d6f1c14910640b58

Tx prefix hash: 8c635d91b9fae60ceddf018b7da02117a2f3cbf5e32044369a87ad45b49d0c5f
Tx public key: d8a993a01a5f0fd887bdb411e980051da13c65cc4c14ed69128d557bc8da351b
Timestamp: 1707149366 Timestamp [UCT]: 2024-02-05 16:09:26 Age [y:d:h:m:s]: 00:344:21:30:05
Block: 951006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246913 RingCT/type: yes/0
Extra: 01d8a993a01a5f0fd887bdb411e980051da13c65cc4c14ed69128d557bc8da351b0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9baf9018dfa7ac7198d69b9af24066b44dfb4120c34819d76d113e301075120 0.600000000000 1409708 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": 951016, "vin": [ { "gen": { "height": 951006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9baf9018dfa7ac7198d69b9af24066b44dfb4120c34819d76d113e301075120" } } ], "extra": [ 1, 216, 169, 147, 160, 26, 95, 15, 216, 135, 189, 180, 17, 233, 128, 5, 29, 161, 60, 101, 204, 76, 20, 237, 105, 18, 141, 85, 123, 200, 218, 53, 27, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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