Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f24d6d4bcc4a14b524465a2db16163589373e62b51bac393afa06beefce4f213

Tx prefix hash: 535e0c0f50b687c8708383877945edf03019c10dcc3cbccf78edf2977f5c2bd8
Tx public key: 7b4ca730adf0538510e8e48ca46b8ec9a442883df944fc4c6f38962f18ae7a76
Timestamp: 1708089254 Timestamp [UCT]: 2024-02-16 13:14:14 Age [y:d:h:m:s]: 01:065:22:48:58
Block: 958808 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308177 RingCT/type: yes/0
Extra: 017b4ca730adf0538510e8e48ca46b8ec9a442883df944fc4c6f38962f18ae7a7602110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6c3d5e49d6305cb3506dc664d6831be5dee3b0fafd30f7c11bdce16380f1b58 0.600000000000 1418169 of 15

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": 958818, "vin": [ { "gen": { "height": 958808 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6c3d5e49d6305cb3506dc664d6831be5dee3b0fafd30f7c11bdce16380f1b58" } } ], "extra": [ 1, 123, 76, 167, 48, 173, 240, 83, 133, 16, 232, 228, 140, 164, 107, 142, 201, 164, 66, 136, 61, 249, 68, 252, 76, 111, 56, 150, 47, 24, 174, 122, 118, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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