Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd103703ccf430019dcce2d1dac5d25143ba4846cbbef2452aa038ec91194e4d

Tx prefix hash: 86987a5a22d7ad2b4977ecdc1ea3c8301336b5e6605c9a5fb087c862f0137a28
Tx public key: fc76ab25f51c232c18c793f569bac241abd152396bbe5bb5f1eda0a60d427e41
Timestamp: 1713949991 Timestamp [UCT]: 2024-04-24 09:13:11 Age [y:d:h:m:s]: 00:247:06:58:44
Block: 1007399 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176999 RingCT/type: yes/0
Extra: 01fc76ab25f51c232c18c793f569bac241abd152396bbe5bb5f1eda0a60d427e410211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b816a018ce4f8fe88d7d67fb59943b1208fd848119adfd3ebc8ec6761e61dd83 0.600000000000 1468727 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": 1007409, "vin": [ { "gen": { "height": 1007399 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b816a018ce4f8fe88d7d67fb59943b1208fd848119adfd3ebc8ec6761e61dd83" } } ], "extra": [ 1, 252, 118, 171, 37, 245, 28, 35, 44, 24, 199, 147, 245, 105, 186, 194, 65, 171, 209, 82, 57, 107, 190, 91, 181, 241, 237, 160, 166, 13, 66, 126, 65, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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