Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94c7cd6630cd2f088d1ac6a400f9216f08795013f17679a55796e90d3c96774e

Tx prefix hash: c2630f96f40a412ed723d93762400a38a307e66f5d969bd373d1a63bcc5d2e28
Tx public key: fae64e0f23b4d6eed4a9292d7b3f3bd02ff232745610dccdbf5a3d1e1d116a2c
Timestamp: 1663040537 Timestamp [UCT]: 2022-09-13 03:42:17 Age [y:d:h:m:s]: 02:124:23:28:08
Block: 586770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 610835 RingCT/type: yes/0
Extra: 01fae64e0f23b4d6eed4a9292d7b3f3bd02ff232745610dccdbf5a3d1e1d116a2c021100000008faf35c9c000000000000000000

1 output(s) for total of 6.978908247000 dcy

stealth address amount amount idx
00: 1699719300b0fc6e4d6ce878e0e2090e3ea625c542a5691ce5c3b96d3e77e68e 6.978908247000 1020911 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": 586780, "vin": [ { "gen": { "height": 586770 } } ], "vout": [ { "amount": 6978908247, "target": { "key": "1699719300b0fc6e4d6ce878e0e2090e3ea625c542a5691ce5c3b96d3e77e68e" } } ], "extra": [ 1, 250, 230, 78, 15, 35, 180, 214, 238, 212, 169, 41, 45, 123, 63, 59, 208, 47, 242, 50, 116, 86, 16, 220, 205, 191, 90, 61, 30, 29, 17, 106, 44, 2, 17, 0, 0, 0, 8, 250, 243, 92, 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