Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57466843f15df1d05d5ddbea5a1d97ff58ba1e3c75d0131d4c2fbf10ccc73409

Tx prefix hash: 696262a1d966963dd0854127b905af18095cb6cc378b54367071ad8da11881f8
Tx public key: eaee43563655d881bca244c4d178061fd5e239e4d2d32f65d9f4b3cbadc3812c
Timestamp: 1622660290 Timestamp [UCT]: 2021-06-02 18:58:10 Age [y:d:h:m:s]: 04:155:12:20:25
Block: 270991 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1133641 RingCT/type: yes/0
Extra: 01eaee43563655d881bca244c4d178061fd5e239e4d2d32f65d9f4b3cbadc3812c0211000000cef120f217000000000000000000

1 output(s) for total of 77.643007764000 dcy

stealth address amount amount idx
00: f3962dc5f9fa0ae41db80a9e8b4addc1226f15e5d88f27fe372f6f48f7bab530 77.643007764000 568667 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": 271001, "vin": [ { "gen": { "height": 270991 } } ], "vout": [ { "amount": 77643007764, "target": { "key": "f3962dc5f9fa0ae41db80a9e8b4addc1226f15e5d88f27fe372f6f48f7bab530" } } ], "extra": [ 1, 234, 238, 67, 86, 54, 85, 216, 129, 188, 162, 68, 196, 209, 120, 6, 31, 213, 226, 57, 228, 210, 211, 47, 101, 217, 244, 179, 203, 173, 195, 129, 44, 2, 17, 0, 0, 0, 206, 241, 32, 242, 23, 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