Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b497df6a290ea049c61a0f23714978e0c7878dec424438e963c171e19618ef88

Tx prefix hash: 02e58fe9ff447e5ab08366160a656df6172bc513c523136e73bedcd3c9692437
Tx public key: cb8b5c6d51243c8129d802c0cbd0ea3de0f9ad4198b81b350a2c9ec427c1e064
Timestamp: 1577811564 Timestamp [UCT]: 2019-12-31 16:59:24 Age [y:d:h:m:s]: 05:160:14:05:40
Block: 35899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1264568 RingCT/type: yes/0
Extra: 01cb8b5c6d51243c8129d802c0cbd0ea3de0f9ad4198b81b350a2c9ec427c1e0640211000000024943cd9f000000000000000000

1 output(s) for total of 466.723915233000 dcy

stealth address amount amount idx
00: 3abdd54fe45e64329c656c0bafb176631149b4ef0b280a78f82d8ed38be1476a 466.723915233000 60624 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": 35909, "vin": [ { "gen": { "height": 35899 } } ], "vout": [ { "amount": 466723915233, "target": { "key": "3abdd54fe45e64329c656c0bafb176631149b4ef0b280a78f82d8ed38be1476a" } } ], "extra": [ 1, 203, 139, 92, 109, 81, 36, 60, 129, 41, 216, 2, 192, 203, 208, 234, 61, 224, 249, 173, 65, 152, 184, 27, 53, 10, 44, 158, 196, 39, 193, 224, 100, 2, 17, 0, 0, 0, 2, 73, 67, 205, 159, 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