Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 311e85422dc647b70c05595f0d43af205090c8f75a85ab901ec47cb55f1a5abe

Tx prefix hash: 967632c20626ea9c07feb2207e7d09f3f77628c334ab9c736fb50749705ccdac
Tx public key: a6a3372b9b9ab222adf3790d59f340a5316f0bfc7f9f432eec07bfdc95f62cf2
Timestamp: 1710719255 Timestamp [UCT]: 2024-03-17 23:47:35 Age [y:d:h:m:s]: 01:239:07:46:33
Block: 980628 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 429732 RingCT/type: yes/0
Extra: 01a6a3372b9b9ab222adf3790d59f340a5316f0bfc7f9f432eec07bfdc95f62cf202110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ee0ffd6a9d93db5bd517a6b8e10c23154ba918410cee289291e802aa16b40af 0.600000000000 1440709 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": 980638, "vin": [ { "gen": { "height": 980628 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ee0ffd6a9d93db5bd517a6b8e10c23154ba918410cee289291e802aa16b40af" } } ], "extra": [ 1, 166, 163, 55, 43, 155, 154, 178, 34, 173, 243, 121, 13, 89, 243, 64, 165, 49, 111, 11, 252, 127, 159, 67, 46, 236, 7, 191, 220, 149, 246, 44, 242, 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