Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a30e6296746536a0d155b0c00ef451c4aa0368c71e08bb0e16570a5a0c01cb1

Tx prefix hash: 853289c25c401b26637c34be74db0ad4fc23f0b349d4b58f58968d42735d14aa
Tx public key: c2f25301c63a622e33cca125d98c7204f7303c060b77d0509c2449b10b0f9b1a
Timestamp: 1635325778 Timestamp [UCT]: 2021-10-27 09:09:38 Age [y:d:h:m:s]: 03:138:14:20:01
Block: 361468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 877268 RingCT/type: yes/0
Extra: 01c2f25301c63a622e33cca125d98c7204f7303c060b77d0509c2449b10b0f9b1a0211000000111154028c000000000000000000

1 output(s) for total of 38.932013947000 dcy

stealth address amount amount idx
00: 2e4ad16e458b84b19ef01b14140aab9b09c90bca97ef8941f62d605afc4b245d 38.932013947000 735398 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": 361478, "vin": [ { "gen": { "height": 361468 } } ], "vout": [ { "amount": 38932013947, "target": { "key": "2e4ad16e458b84b19ef01b14140aab9b09c90bca97ef8941f62d605afc4b245d" } } ], "extra": [ 1, 194, 242, 83, 1, 198, 58, 98, 46, 51, 204, 161, 37, 217, 140, 114, 4, 247, 48, 60, 6, 11, 119, 208, 80, 156, 36, 73, 177, 11, 15, 155, 26, 2, 17, 0, 0, 0, 17, 17, 84, 2, 140, 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