Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f6b4ec9d15615b429836a411e0e7d0c525db8aaefeffbbb0fc66d2352ec95ec

Tx prefix hash: e3ed7b27bee23cc9b61cd3b701e629e42aeee4dd5bf5615eb702d467d230fb3c
Tx public key: f159b45265def5e821e7976ed3756064c24c267e842223aba8b0517bf146f9e1
Timestamp: 1705243640 Timestamp [UCT]: 2024-01-14 14:47:20 Age [y:d:h:m:s]: 01:071:13:11:09
Block: 935212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312207 RingCT/type: yes/0
Extra: 01f159b45265def5e821e7976ed3756064c24c267e842223aba8b0517bf146f9e10211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1d3da3986cfaf9efa2baa07b5f2b1b35eaa0cdd806d153af109ca01b419bd1f 0.600000000000 1393228 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": 935222, "vin": [ { "gen": { "height": 935212 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1d3da3986cfaf9efa2baa07b5f2b1b35eaa0cdd806d153af109ca01b419bd1f" } } ], "extra": [ 1, 241, 89, 180, 82, 101, 222, 245, 232, 33, 231, 151, 110, 211, 117, 96, 100, 194, 76, 38, 126, 132, 34, 35, 171, 168, 176, 81, 123, 241, 70, 249, 225, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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