Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d925379b7637af608781551d47bcbf162606375fcf4e12705cda9b54e1f66be0

Tx prefix hash: dce1d73aaa20c650705346c603ca21fe3afae3fbd6199d7b796631fa7d5e6ed5
Tx public key: 0549e45a2d5c37a2fefad2617eda5cd893a4d59c26189f6f32f9c7b9b4b1ebc5
Timestamp: 1577185407 Timestamp [UCT]: 2019-12-24 11:03:27 Age [y:d:h:m:s]: 05:081:11:54:58
Block: 30625 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1208091 RingCT/type: yes/0
Extra: 010549e45a2d5c37a2fefad2617eda5cd893a4d59c26189f6f32f9c7b9b4b1ebc50211000000014ac5aa02000000000000000000

1 output(s) for total of 485.878322404000 dcy

stealth address amount amount idx
00: 3a4c63dc54057ef3aff8695c3c8423dc0aeb0caa3b866ec3ffebbf6b1d9cee2b 485.878322404000 50567 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": 30635, "vin": [ { "gen": { "height": 30625 } } ], "vout": [ { "amount": 485878322404, "target": { "key": "3a4c63dc54057ef3aff8695c3c8423dc0aeb0caa3b866ec3ffebbf6b1d9cee2b" } } ], "extra": [ 1, 5, 73, 228, 90, 45, 92, 55, 162, 254, 250, 210, 97, 126, 218, 92, 216, 147, 164, 213, 156, 38, 24, 159, 111, 50, 249, 199, 185, 180, 177, 235, 197, 2, 17, 0, 0, 0, 1, 74, 197, 170, 2, 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