Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4653443348892a1062f927c7de32025500a5d43f7ff5a0a660fc46f8f7ef40ae

Tx prefix hash: 696b1e1862b24f0d318c6100c7ec7c76494d7cec07f03fa2cbd008af2561f4cf
Tx public key: bdb1f02e9f8517fa9019f71b98662277ed64b4eac61b683dcab3311e245ebcd4
Timestamp: 1630362210 Timestamp [UCT]: 2021-08-30 22:23:30 Age [y:d:h:m:s]: 03:137:18:23:04
Block: 324127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 873177 RingCT/type: yes/0
Extra: 01bdb1f02e9f8517fa9019f71b98662277ed64b4eac61b683dcab3311e245ebcd40211000000237062e8e6000000000000000000

1 output(s) for total of 51.764634588000 dcy

stealth address amount amount idx
00: 3379acc306f05b177be179dd8b3a3473aafec43e46f71b29b8a97024e5b7bca0 51.764634588000 672126 of 0

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": 324137, "vin": [ { "gen": { "height": 324127 } } ], "vout": [ { "amount": 51764634588, "target": { "key": "3379acc306f05b177be179dd8b3a3473aafec43e46f71b29b8a97024e5b7bca0" } } ], "extra": [ 1, 189, 177, 240, 46, 159, 133, 23, 250, 144, 25, 247, 27, 152, 102, 34, 119, 237, 100, 180, 234, 198, 27, 104, 61, 202, 179, 49, 30, 36, 94, 188, 212, 2, 17, 0, 0, 0, 35, 112, 98, 232, 230, 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