Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bd4674524e147fb7657b07dee8c93acb8a4431d2a7c4097d853f05f2942a01d

Tx prefix hash: f5497a9dd9ccfccb1964468cd3e7cb677c93a46619a0dbc51e25d39d3e2a111a
Tx public key: 31ed23b64309e9cd4a36ddf394879d7665f03982c49c800a7cd512c0f08739a3
Timestamp: 1739466924 Timestamp [UCT]: 2025-02-13 17:15:24 Age [y:d:h:m:s]: 00:329:12:44:38
Block: 1218510 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233340 RingCT/type: yes/0
Extra: 0131ed23b64309e9cd4a36ddf394879d7665f03982c49c800a7cd512c0f08739a3021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af52e27d9cfcded74c8a451e026a1bd0404ee5ef4c0b772a60d23f1cabaf119a 0.600000000000 1705329 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": 1218520, "vin": [ { "gen": { "height": 1218510 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af52e27d9cfcded74c8a451e026a1bd0404ee5ef4c0b772a60d23f1cabaf119a" } } ], "extra": [ 1, 49, 237, 35, 182, 67, 9, 233, 205, 74, 54, 221, 243, 148, 135, 157, 118, 101, 240, 57, 130, 196, 156, 128, 10, 124, 213, 18, 192, 240, 135, 57, 163, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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