Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e77557b5b08a618dad3f16b33b8a37ceb60f480b24241f4ac3341d109dc038fb

Tx prefix hash: f1b70bea944ad9dbe755b235f53447aab90533de6ec7eae4f83d7be303f81e47
Tx public key: aa8e70db1b2b0fd135c14feebee8999e0646981805491e84bf51a998769c2073
Timestamp: 1707830634 Timestamp [UCT]: 2024-02-13 13:23:54 Age [y:d:h:m:s]: 01:042:00:16:10
Block: 956661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291054 RingCT/type: yes/0
Extra: 01aa8e70db1b2b0fd135c14feebee8999e0646981805491e84bf51a998769c20730211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b0648b163074771b0e94c7f03ea6ce8c001aa296453a2cf87a053cc4f1f5fdd 0.600000000000 1415971 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": 956671, "vin": [ { "gen": { "height": 956661 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b0648b163074771b0e94c7f03ea6ce8c001aa296453a2cf87a053cc4f1f5fdd" } } ], "extra": [ 1, 170, 142, 112, 219, 27, 43, 15, 209, 53, 193, 79, 238, 190, 232, 153, 158, 6, 70, 152, 24, 5, 73, 30, 132, 191, 81, 169, 152, 118, 156, 32, 115, 2, 17, 0, 0, 0, 7, 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