Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7ebfd4c5aba8c2caa76dd7895da65f50792cce0f09bb8cd7322b76e24aab9ad

Tx prefix hash: 04bc8873a1d1867bab93c1e4b5ffb4c76a5619999af06b515fdfc99ebfdd5a06
Tx public key: c34c92c1e6988834d5d50cb7f09946d26cab76da246c452cc1b5a9e3876d3751
Timestamp: 1739129192 Timestamp [UCT]: 2025-02-09 19:26:32 Age [y:d:h:m:s]: 00:346:06:39:32
Block: 1215706 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245191 RingCT/type: yes/0
Extra: 01c34c92c1e6988834d5d50cb7f09946d26cab76da246c452cc1b5a9e3876d3751021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae6b9c30da347c4772bf0cde215c253dddabaddfdc42aedbfd567489ce093a0d 0.600000000000 1702505 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": 1215716, "vin": [ { "gen": { "height": 1215706 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae6b9c30da347c4772bf0cde215c253dddabaddfdc42aedbfd567489ce093a0d" } } ], "extra": [ 1, 195, 76, 146, 193, 230, 152, 136, 52, 213, 213, 12, 183, 240, 153, 70, 210, 108, 171, 118, 218, 36, 108, 69, 44, 193, 181, 169, 227, 135, 109, 55, 81, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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