Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ee0b8fa07c2c617a82fca98ebed824291cb4566b6769c582ad66d9fac0f44b9

Tx prefix hash: 7ba3323fe28e1355dd029ce8479966aee0e3439746f76c5537ca668bf6807f95
Tx public key: da204c9c8dd209b5d131de2b6fe5efe0d4bbda9fe1bb160397149661a4d5c79f
Timestamp: 1675451881 Timestamp [UCT]: 2023-02-03 19:18:01 Age [y:d:h:m:s]: 02:103:07:17:30
Block: 689112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 595475 RingCT/type: yes/0
Extra: 01da204c9c8dd209b5d131de2b6fe5efe0d4bbda9fe1bb160397149661a4d5c79f0211000000015029cbac000000000000000000

1 output(s) for total of 3.196581703000 dcy

stealth address amount amount idx
00: af56adfad62819330d3a70b3c47ca0bf8c14e4dd01c8859d8a36a812386f5b40 3.196581703000 1131776 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": 689122, "vin": [ { "gen": { "height": 689112 } } ], "vout": [ { "amount": 3196581703, "target": { "key": "af56adfad62819330d3a70b3c47ca0bf8c14e4dd01c8859d8a36a812386f5b40" } } ], "extra": [ 1, 218, 32, 76, 156, 141, 210, 9, 181, 209, 49, 222, 43, 111, 229, 239, 224, 212, 187, 218, 159, 225, 187, 22, 3, 151, 20, 150, 97, 164, 213, 199, 159, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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