Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17bff40752a949a4bfa1057f11fbd8517807d118a5dd95951722b8c623f9c1ea

Tx prefix hash: de023349a01efabe9edf7fcc6bec1e2024d8296c3ca92038aeea7b2c553dee66
Tx public key: 63a1e83f2ae1410f4c16208265f4a765e3f15e9aa6d66a224a6652a4f452a9aa
Timestamp: 1718986048 Timestamp [UCT]: 2024-06-21 16:07:28 Age [y:d:h:m:s]: 00:293:06:51:54
Block: 1049127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209598 RingCT/type: yes/0
Extra: 0163a1e83f2ae1410f4c16208265f4a765e3f15e9aa6d66a224a6652a4f452a9aa02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5cb43fc43341b0eae21c4ef4fe1d2bbf622aa9410dfcad7c34d26ba4415bff7 0.600000000000 1519224 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": 1049137, "vin": [ { "gen": { "height": 1049127 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5cb43fc43341b0eae21c4ef4fe1d2bbf622aa9410dfcad7c34d26ba4415bff7" } } ], "extra": [ 1, 99, 161, 232, 63, 42, 225, 65, 15, 76, 22, 32, 130, 101, 244, 167, 101, 227, 241, 94, 154, 166, 214, 106, 34, 74, 102, 82, 164, 244, 82, 169, 170, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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