Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 587ca6d6a819eb84418086d4b7a19a10f51a6e79efbaa9dff3eff5dd262e5d4e

Tx prefix hash: 1a31caecec1e175a4974844db59808ac066ba0c1d2f9fe6d559a8b6d75122ca2
Tx public key: b26d8502bfe25cdfc8211888e0ff8464fcfb74d3115c6639d238bbf9f9107bf7
Timestamp: 1714689773 Timestamp [UCT]: 2024-05-02 22:42:53 Age [y:d:h:m:s]: 00:142:00:08:14
Block: 1013539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101711 RingCT/type: yes/0
Extra: 01b26d8502bfe25cdfc8211888e0ff8464fcfb74d3115c6639d238bbf9f9107bf702110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ccf9e2b72f75a07fa3dabebe7ae61f7b149b60a68a8961540e32179c6d7294aa 0.600000000000 1476382 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": 1013549, "vin": [ { "gen": { "height": 1013539 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ccf9e2b72f75a07fa3dabebe7ae61f7b149b60a68a8961540e32179c6d7294aa" } } ], "extra": [ 1, 178, 109, 133, 2, 191, 226, 92, 223, 200, 33, 24, 136, 224, 255, 132, 100, 252, 251, 116, 211, 17, 92, 102, 57, 210, 56, 187, 249, 249, 16, 123, 247, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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