Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d771d554b1ecc3a3b61d0e6c333970410f38e9cd8e337c0addefa07f24d313f

Tx prefix hash: 65935ceefe4eebb61d5fa32be552a8a3b28a82fedfc623859684815a59f055fc
Tx public key: a49723f3978b6fd2a54e77649c75fe26cb50a290f0094c78e2c897e6c8aae19e
Timestamp: 1660941923 Timestamp [UCT]: 2022-08-19 20:45:23 Age [y:d:h:m:s]: 02:126:08:23:52
Block: 569477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 611771 RingCT/type: yes/0
Extra: 01a49723f3978b6fd2a54e77649c75fe26cb50a290f0094c78e2c897e6c8aae19e021100000009e6d27f9c000000000000000000

1 output(s) for total of 7.963177597000 dcy

stealth address amount amount idx
00: c0cfe69fbbe967a0a12e9abf9caab9f2368c596de13c51fd0ade3efc00eb9fc0 7.963177597000 1002626 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": 569487, "vin": [ { "gen": { "height": 569477 } } ], "vout": [ { "amount": 7963177597, "target": { "key": "c0cfe69fbbe967a0a12e9abf9caab9f2368c596de13c51fd0ade3efc00eb9fc0" } } ], "extra": [ 1, 164, 151, 35, 243, 151, 139, 111, 210, 165, 78, 119, 100, 156, 117, 254, 38, 203, 80, 162, 144, 240, 9, 76, 120, 226, 200, 151, 230, 200, 170, 225, 158, 2, 17, 0, 0, 0, 9, 230, 210, 127, 156, 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