Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce176866c88440a0208b209daf55526bd6324f0378e1626e8447fca9e86816b7

Tx prefix hash: 931f0094677ab5daabe7039669c1dfbb561ec9501222191d752e409f9dae1774
Tx public key: 9ada7df5ee89706cb7a7b2f25ddb6261db612b295edacc1dc55e5899b8e8756e
Timestamp: 1582964487 Timestamp [UCT]: 2020-02-29 08:21:27 Age [y:d:h:m:s]: 05:253:14:59:02
Block: 73831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1333426 RingCT/type: yes/0
Extra: 019ada7df5ee89706cb7a7b2f25ddb6261db612b295edacc1dc55e5899b8e8756e0211000000370aca7173000000000000000000

1 output(s) for total of 349.436323402000 dcy

stealth address amount amount idx
00: 34febde91ae5cc9c37c82804723c8f3ab30289993bda07374c3dfe599e8599d9 349.436323402000 136394 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": 73841, "vin": [ { "gen": { "height": 73831 } } ], "vout": [ { "amount": 349436323402, "target": { "key": "34febde91ae5cc9c37c82804723c8f3ab30289993bda07374c3dfe599e8599d9" } } ], "extra": [ 1, 154, 218, 125, 245, 238, 137, 112, 108, 183, 167, 178, 242, 93, 219, 98, 97, 219, 97, 43, 41, 94, 218, 204, 29, 197, 94, 88, 153, 184, 232, 117, 110, 2, 17, 0, 0, 0, 55, 10, 202, 113, 115, 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