Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8089a12def5e2893b5ad908c64c18bd3971ae4e588f2093488d5d0a6857e46c6

Tx prefix hash: 2dc7c75503f2f6711f659e1b41f08f4dd641d9176ba690c54af4b6596fb099d9
Tx public key: dbadce919e1b7c03a6685e84f8cdd0705aca761d044762c1f73438ccc9fa6e27
Timestamp: 1727893509 Timestamp [UCT]: 2024-10-02 18:25:09 Age [y:d:h:m:s]: 00:251:04:52:56
Block: 1123009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179369 RingCT/type: yes/0
Extra: 01dbadce919e1b7c03a6685e84f8cdd0705aca761d044762c1f73438ccc9fa6e2702110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5bc8f6118dea507348b8af89a229e4aacd994ab94c3aa78ee382f18efd71233 0.600000000000 1605542 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": 1123019, "vin": [ { "gen": { "height": 1123009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5bc8f6118dea507348b8af89a229e4aacd994ab94c3aa78ee382f18efd71233" } } ], "extra": [ 1, 219, 173, 206, 145, 158, 27, 124, 3, 166, 104, 94, 132, 248, 205, 208, 112, 90, 202, 118, 29, 4, 71, 98, 193, 247, 52, 56, 204, 201, 250, 110, 39, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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