Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 679cf44db3ccc9fc2efaeb2b44e7f1a5fb6d190e3a1cadf64d5c8d1e6f38d291

Tx prefix hash: 68e319e8a7ada516c2faa9e225f8f2b1551744ecaf189605d92c9011dcefca71
Tx public key: 557fd5e3f5b176e934db7a64e13638182285fab5ad8d2c1bf0ba3c5d1fa9998b
Timestamp: 1698102985 Timestamp [UCT]: 2023-10-23 23:16:25 Age [y:d:h:m:s]: 01:203:03:46:57
Block: 876225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406238 RingCT/type: yes/0
Extra: 01557fd5e3f5b176e934db7a64e13638182285fab5ad8d2c1bf0ba3c5d1fa9998b021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.766836639000 dcy

stealth address amount amount idx
00: adbdf13b31480170d8e66ccf16c7bd3357513faa7e8538343e6c2793bf4d9ad4 0.766836639000 1331539 of 0

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": 876235, "vin": [ { "gen": { "height": 876225 } } ], "vout": [ { "amount": 766836639, "target": { "key": "adbdf13b31480170d8e66ccf16c7bd3357513faa7e8538343e6c2793bf4d9ad4" } } ], "extra": [ 1, 85, 127, 213, 227, 245, 177, 118, 233, 52, 219, 122, 100, 225, 54, 56, 24, 34, 133, 250, 181, 173, 141, 44, 27, 240, 186, 60, 93, 31, 169, 153, 139, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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