Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb1f712dfa90a918f7f7f0b5e06d87bcf400d0f595fd94782e0e555ca1375636

Tx prefix hash: 04576d44ebfb16240c89fc9e64a62932c0144f5be9a0a60690285ec920b34c4d
Tx public key: 4687d23fe878483f9486596999cfd0d43ee0e820d67592539a503a5e543c141a
Timestamp: 1579193700 Timestamp [UCT]: 2020-01-16 16:55:00 Age [y:d:h:m:s]: 05:049:01:26:10
Block: 46962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1185167 RingCT/type: yes/0
Extra: 014687d23fe878483f9486596999cfd0d43ee0e820d67592539a503a5e543c141a0211000000038a2ee0d9000000000000000000

1 output(s) for total of 428.939692963000 dcy

stealth address amount amount idx
00: dada8eec198f54374b61efe244d62b9cbc23fd99843a4e0eb2a77e6db219fec8 428.939692963000 86646 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": 46972, "vin": [ { "gen": { "height": 46962 } } ], "vout": [ { "amount": 428939692963, "target": { "key": "dada8eec198f54374b61efe244d62b9cbc23fd99843a4e0eb2a77e6db219fec8" } } ], "extra": [ 1, 70, 135, 210, 63, 232, 120, 72, 63, 148, 134, 89, 105, 153, 207, 208, 212, 62, 224, 232, 32, 214, 117, 146, 83, 154, 80, 58, 94, 84, 60, 20, 26, 2, 17, 0, 0, 0, 3, 138, 46, 224, 217, 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