Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5f75c18cbdc865ff5f2e5c89682554cb13df7b060c9f1e1100f7341d00d1232

Tx prefix hash: ef2a68634e1c4698edc276cb7168e31ec4ae55fecf7bad38a38adc84b91f8040
Tx public key: 641a70ab6fcde77bec35b26c996a57c31e03d143e92b6db46f186d6bdc48fbc8
Timestamp: 1581905409 Timestamp [UCT]: 2020-02-17 02:10:09 Age [y:d:h:m:s]: 04:263:03:38:30
Block: 66456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1080427 RingCT/type: yes/0
Extra: 01641a70ab6fcde77bec35b26c996a57c31e03d143e92b6db46f186d6bdc48fbc802110000000103d36d11000000000000000000

1 output(s) for total of 369.678281714000 dcy

stealth address amount amount idx
00: c00f009534131114ba68e9aaed87dbb3d489900e474a35b63b47bd4010aeb531 369.678281714000 122407 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": 66466, "vin": [ { "gen": { "height": 66456 } } ], "vout": [ { "amount": 369678281714, "target": { "key": "c00f009534131114ba68e9aaed87dbb3d489900e474a35b63b47bd4010aeb531" } } ], "extra": [ 1, 100, 26, 112, 171, 111, 205, 231, 123, 236, 53, 178, 108, 153, 106, 87, 195, 30, 3, 209, 67, 233, 43, 109, 180, 111, 24, 109, 107, 220, 72, 251, 200, 2, 17, 0, 0, 0, 1, 3, 211, 109, 17, 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