Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5892cf373802c2acb7545c122f5eb07553ccf013589ae40c834e46dfa3e61d7

Tx prefix hash: 7e9e6fe0fa6e2f1c506f777a0788e9abce0fa1e38197dfa0b677424401c381c9
Tx public key: 89b75052f32785079595a00c465e80c316adf4f2086e2fb0a6efeab30e351b9d
Timestamp: 1734279925 Timestamp [UCT]: 2024-12-15 16:25:25 Age [y:d:h:m:s]: 00:095:12:23:33
Block: 1175851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68049 RingCT/type: yes/0
Extra: 0189b75052f32785079595a00c465e80c316adf4f2086e2fb0a6efeab30e351b9d021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 084b6d05a24992022e81e6242a7cd25bbd4ff12faa1fce43997d1ff81c0bbecb 0.600000000000 1662178 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": 1175861, "vin": [ { "gen": { "height": 1175851 } } ], "vout": [ { "amount": 600000000, "target": { "key": "084b6d05a24992022e81e6242a7cd25bbd4ff12faa1fce43997d1ff81c0bbecb" } } ], "extra": [ 1, 137, 183, 80, 82, 243, 39, 133, 7, 149, 149, 160, 12, 70, 94, 128, 195, 22, 173, 244, 242, 8, 110, 47, 176, 166, 239, 234, 179, 14, 53, 27, 157, 2, 17, 0, 0, 0, 6, 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