Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 860689ac6303da05dbf45cd1a98e4dbdfd9ed651afb75c818982f3befdaadc3f

Tx prefix hash: c5ed7dcec423ffec0269664c324efbfe22b6930476d0adfa2e4bcd835cc7ed4c
Tx public key: 060e66d6ac07199a351d6fdf0189d3076cf59fb9dc6abcda886c4692ff1703ef
Timestamp: 1738169876 Timestamp [UCT]: 2025-01-29 16:57:56 Age [y:d:h:m:s]: 00:296:00:52:17
Block: 1207779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209325 RingCT/type: yes/0
Extra: 01060e66d6ac07199a351d6fdf0189d3076cf59fb9dc6abcda886c4692ff1703ef0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0587f9dea2a79aaf1bea71ac6cf89fb72aae18f8786400b5c5d089bf3ea98bc5 0.600000000000 1694504 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": 1207789, "vin": [ { "gen": { "height": 1207779 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0587f9dea2a79aaf1bea71ac6cf89fb72aae18f8786400b5c5d089bf3ea98bc5" } } ], "extra": [ 1, 6, 14, 102, 214, 172, 7, 25, 154, 53, 29, 111, 223, 1, 137, 211, 7, 108, 245, 159, 185, 220, 106, 188, 218, 136, 108, 70, 146, 255, 23, 3, 239, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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