Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e5588c4051de6ac4ee4bc7780b15423d303c6e6f9291e6dd38c38017328e9a9

Tx prefix hash: 416752e98e54d564c2b7d97fba7fbefe0a194e4e5b096abf3ca6feaea079a2f5
Tx public key: 137a4c10cacbb5e10840956e56671373a6a56af0bb4cec2e217801e883b5f569
Timestamp: 1729384302 Timestamp [UCT]: 2024-10-20 00:31:42 Age [y:d:h:m:s]: 00:246:06:32:31
Block: 1135347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175630 RingCT/type: yes/0
Extra: 01137a4c10cacbb5e10840956e56671373a6a56af0bb4cec2e217801e883b5f569021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a99d40653f94b9fdfe3fa238e3c70ea2fb098af5886f8bbae164d2fa77ddb8a 0.600000000000 1618684 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": 1135357, "vin": [ { "gen": { "height": 1135347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a99d40653f94b9fdfe3fa238e3c70ea2fb098af5886f8bbae164d2fa77ddb8a" } } ], "extra": [ 1, 19, 122, 76, 16, 202, 203, 181, 225, 8, 64, 149, 110, 86, 103, 19, 115, 166, 165, 106, 240, 187, 76, 236, 46, 33, 120, 1, 232, 131, 181, 245, 105, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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