Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc44a556ee3bb1e702f5d0c6bf21040aee0ea8f18e20221085be5d6b46b7e657

Tx prefix hash: 68f8c88707d3eb15b45871fb04240971847d1ac8249f08c3b52b7fbf43bca380
Tx public key: 2fa70c418354b04191fb311c0d4ae3b390cbf348663c364cdb523592700210b9
Timestamp: 1725024934 Timestamp [UCT]: 2024-08-30 13:35:34 Age [y:d:h:m:s]: 01:093:13:31:00
Block: 1099209 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325344 RingCT/type: yes/0
Extra: 012fa70c418354b04191fb311c0d4ae3b390cbf348663c364cdb523592700210b902110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f018512eb6b5ead101c42d94f5653503b8ed20e857aea0013d7f19c435e0238 0.600000000000 1575146 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": 1099219, "vin": [ { "gen": { "height": 1099209 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f018512eb6b5ead101c42d94f5653503b8ed20e857aea0013d7f19c435e0238" } } ], "extra": [ 1, 47, 167, 12, 65, 131, 84, 176, 65, 145, 251, 49, 28, 13, 74, 227, 179, 144, 203, 243, 72, 102, 60, 54, 76, 219, 82, 53, 146, 112, 2, 16, 185, 2, 17, 0, 0, 0, 1, 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