Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 455dfb94ada357067ce52a8621642f3ebf5c1e3bf66103a4c060b3c264ac4724

Tx prefix hash: 8deec40be5d2d1b5d9c723cae19e4665a1ec9d7ef117bceb3a0aaa2e73bd6bd7
Tx public key: f5d06baa8329c36cd8ff3a56b7aeee7ee8a6652aebb8d0861d10f8b0fc62237c
Timestamp: 1696664056 Timestamp [UCT]: 2023-10-07 07:34:16 Age [y:d:h:m:s]: 02:033:03:34:42
Block: 864290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 543310 RingCT/type: yes/0
Extra: 01f5d06baa8329c36cd8ff3a56b7aeee7ee8a6652aebb8d0861d10f8b0fc62237c021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.839940421000 dcy

stealth address amount amount idx
00: bbdb3cbcbdeaa5ac14235bc384f84a335fa1975de06ccd4ca03e92a7b84c1d29 0.839940421000 1318802 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": 864300, "vin": [ { "gen": { "height": 864290 } } ], "vout": [ { "amount": 839940421, "target": { "key": "bbdb3cbcbdeaa5ac14235bc384f84a335fa1975de06ccd4ca03e92a7b84c1d29" } } ], "extra": [ 1, 245, 208, 107, 170, 131, 41, 195, 108, 216, 255, 58, 86, 183, 174, 238, 126, 232, 166, 101, 42, 235, 184, 208, 134, 29, 16, 248, 176, 252, 98, 35, 124, 2, 17, 0, 0, 0, 1, 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