Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 168b6ff4df4c591b1bf5f8d1517b1878cf56b5e1b75cfeee0d8c1034f0c17d60

Tx prefix hash: 28dd9b63b4f3039ef2fea54796f785701d76f0cda8da0b4e71f87fbaf868abbd
Tx public key: 43c661f88da265e68fcca729e39724c53ad4966da9ec2e19ab69c73d21214ce3
Timestamp: 1579013522 Timestamp [UCT]: 2020-01-14 14:52:02 Age [y:d:h:m:s]: 05:002:09:13:21
Block: 45362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1152143 RingCT/type: yes/0
Extra: 0143c661f88da265e68fcca729e39724c53ad4966da9ec2e19ab69c73d21214ce30211000000124ac5aa02000000000000000000

1 output(s) for total of 434.207882353000 dcy

stealth address amount amount idx
00: 3cd1c5a486737ed8bd1a90ff4667ad231f1fb988898bf245521e8d9c33c00fef 434.207882353000 82859 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": 45372, "vin": [ { "gen": { "height": 45362 } } ], "vout": [ { "amount": 434207882353, "target": { "key": "3cd1c5a486737ed8bd1a90ff4667ad231f1fb988898bf245521e8d9c33c00fef" } } ], "extra": [ 1, 67, 198, 97, 248, 141, 162, 101, 230, 143, 204, 167, 41, 227, 151, 36, 197, 58, 212, 150, 109, 169, 236, 46, 25, 171, 105, 199, 61, 33, 33, 76, 227, 2, 17, 0, 0, 0, 18, 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