Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49b8ce995a1c67a0f5dd4b136aac08057387c8c761bbfa2546c04bffdf58cac9

Tx prefix hash: 66bf2eff8fe09d2bae2d2ea72a48bb6a6518c1a1bbc61602121475da0161d009
Tx public key: 339a79fbb1d64ada0bf4bf3ea761cdae8c2bfd87d3cd4efc2be0b0e11802f4b7
Timestamp: 1712608464 Timestamp [UCT]: 2024-04-08 20:34:24 Age [y:d:h:m:s]: 01:020:22:27:19
Block: 996244 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275964 RingCT/type: yes/0
Extra: 01339a79fbb1d64ada0bf4bf3ea761cdae8c2bfd87d3cd4efc2be0b0e11802f4b702110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 850b8ddede4f12eeb55eabc5c81d8a2176135b69951e65c55e153b2a83fd6e9d 0.600000000000 1456660 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": 996254, "vin": [ { "gen": { "height": 996244 } } ], "vout": [ { "amount": 600000000, "target": { "key": "850b8ddede4f12eeb55eabc5c81d8a2176135b69951e65c55e153b2a83fd6e9d" } } ], "extra": [ 1, 51, 154, 121, 251, 177, 214, 74, 218, 11, 244, 191, 62, 167, 97, 205, 174, 140, 43, 253, 135, 211, 205, 78, 252, 43, 224, 176, 225, 24, 2, 244, 183, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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