Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55bddf0f2c054eb672ee4ea50c70c27399abaeec7760c681ee429584044465db

Tx prefix hash: 8d412d172f964eb3baf4d64e801886406a2895f8ce3de6ae3e4f55f6a5a8923b
Tx public key: fa584f5860da3d64ae72023788bda824d092b3cbae4730d3a569bda234bdc1b8
Timestamp: 1720976350 Timestamp [UCT]: 2024-07-14 16:59:10 Age [y:d:h:m:s]: 00:269:22:33:36
Block: 1065660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192846 RingCT/type: yes/0
Extra: 01fa584f5860da3d64ae72023788bda824d092b3cbae4730d3a569bda234bdc1b802110000001991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83ba229423b6139a433ec7bb07232cccd0c85adc35f5ab8a3dcbe5f49d2cddfd 0.600000000000 1536209 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": 1065670, "vin": [ { "gen": { "height": 1065660 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83ba229423b6139a433ec7bb07232cccd0c85adc35f5ab8a3dcbe5f49d2cddfd" } } ], "extra": [ 1, 250, 88, 79, 88, 96, 218, 61, 100, 174, 114, 2, 55, 136, 189, 168, 36, 208, 146, 179, 203, 174, 71, 48, 211, 165, 105, 189, 162, 52, 189, 193, 184, 2, 17, 0, 0, 0, 25, 145, 225, 60, 4, 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