Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bcfe96a663c4110462c170162a92c07af70a284bfaf8a77295970b40610c042

Tx prefix hash: 572b6ae3942d499e7ed7bbfd99dab427111e02628bd2a017445cdda497b60513
Tx public key: 66523b8289afe33eac7f6b1578f2f10e3ad8d0c89d2e2c7d642f61d5392d0f11
Timestamp: 1734467844 Timestamp [UCT]: 2024-12-17 20:37:24 Age [y:d:h:m:s]: 00:018:09:34:57
Block: 1177414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13144 RingCT/type: yes/0
Extra: 0166523b8289afe33eac7f6b1578f2f10e3ad8d0c89d2e2c7d642f61d5392d0f110211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a4bf3472b3ef285c4482ac2b458cc36ffeb2eb662eeb605cfc4b22e49521f24 0.600000000000 1663785 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": 1177424, "vin": [ { "gen": { "height": 1177414 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a4bf3472b3ef285c4482ac2b458cc36ffeb2eb662eeb605cfc4b22e49521f24" } } ], "extra": [ 1, 102, 82, 59, 130, 137, 175, 227, 62, 172, 127, 107, 21, 120, 242, 241, 14, 58, 216, 208, 200, 157, 46, 44, 125, 100, 47, 97, 213, 57, 45, 15, 17, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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