Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f194087bbf2b5e0fd6db54f60e566a3667b883f0ba1d304aea13e8430c7b1ec

Tx prefix hash: a4f48ae44df0c6a04be29d6ada27d9806a94ac795c7e9fe3d958e6acbfeb4b6e
Tx public key: a43faf2bbac9e3b64ddd28cafe79189eaabbcc0e9fa5b50869547db92cf2c116
Timestamp: 1718586844 Timestamp [UCT]: 2024-06-17 01:14:04 Age [y:d:h:m:s]: 01:144:23:48:25
Block: 1045855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362164 RingCT/type: yes/0
Extra: 01a43faf2bbac9e3b64ddd28cafe79189eaabbcc0e9fa5b50869547db92cf2c116021100000001c9b917ea000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3803a744265efbe44fc107b6643aebfb9e62c01c26adf4371dac4015b52bbc6 0.600000000000 1515550 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": 1045865, "vin": [ { "gen": { "height": 1045855 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3803a744265efbe44fc107b6643aebfb9e62c01c26adf4371dac4015b52bbc6" } } ], "extra": [ 1, 164, 63, 175, 43, 186, 201, 227, 182, 77, 221, 40, 202, 254, 121, 24, 158, 170, 187, 204, 14, 159, 165, 181, 8, 105, 84, 125, 185, 44, 242, 193, 22, 2, 17, 0, 0, 0, 1, 201, 185, 23, 234, 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