Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50a6268bb3f89ecdc9ae7a06168f431f0d5a009a4236afc4c8b9770c7461e020

Tx prefix hash: 8e453eebc43b4ea06f081603e735eb4d4f94e66fc381beb9a9a105db8044930a
Tx public key: b6ce5422262b678cdf1802525095d76e87df540f6043e157096d81a0d250b51c
Timestamp: 1582193563 Timestamp [UCT]: 2020-02-20 10:12:43 Age [y:d:h:m:s]: 05:059:00:19:09
Block: 68704 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1195381 RingCT/type: yes/0
Extra: 01b6ce5422262b678cdf1802525095d76e87df540f6043e157096d81a0d250b51c02110000000156c366d3000000000000000000

1 output(s) for total of 363.375743337000 dcy

stealth address amount amount idx
00: 1774b6b233c2fdff2ce6cde738dd20e3f444de645fd5862a2d69bc97264e5f6e 363.375743337000 126665 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": 68714, "vin": [ { "gen": { "height": 68704 } } ], "vout": [ { "amount": 363375743337, "target": { "key": "1774b6b233c2fdff2ce6cde738dd20e3f444de645fd5862a2d69bc97264e5f6e" } } ], "extra": [ 1, 182, 206, 84, 34, 38, 43, 103, 140, 223, 24, 2, 82, 80, 149, 215, 110, 135, 223, 84, 15, 96, 67, 225, 87, 9, 109, 129, 160, 210, 80, 181, 28, 2, 17, 0, 0, 0, 1, 86, 195, 102, 211, 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