Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf28e8cb695154a24340eb00c35bb612c4244fdd1938efdeae75bde25fc5c531

Tx prefix hash: 25c3ff546254a8a43a0fe712704b8bb90870a64fecfbc297d703bc618d87b04e
Tx public key: ffb26cb4262a2514dc74f8de3da46e90be0f88eeaa75cb77295a2d299d2765aa
Timestamp: 1728691423 Timestamp [UCT]: 2024-10-12 00:03:43 Age [y:d:h:m:s]: 01:054:02:21:04
Block: 1129616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297076 RingCT/type: yes/0
Extra: 01ffb26cb4262a2514dc74f8de3da46e90be0f88eeaa75cb77295a2d299d2765aa0211000000023cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7aa67455bce4e08be60e01551ee0b8b66f942b47fa9a173cbeccbdd863c0825 0.600000000000 1612447 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": 1129626, "vin": [ { "gen": { "height": 1129616 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7aa67455bce4e08be60e01551ee0b8b66f942b47fa9a173cbeccbdd863c0825" } } ], "extra": [ 1, 255, 178, 108, 180, 38, 42, 37, 20, 220, 116, 248, 222, 61, 164, 110, 144, 190, 15, 136, 238, 170, 117, 203, 119, 41, 90, 45, 41, 157, 39, 101, 170, 2, 17, 0, 0, 0, 2, 60, 208, 252, 6, 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