Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14128c665b174a1c6b589ea101283cba9b4dc885f59ed0ec386d5159193023db

Tx prefix hash: fc80fb4b0013f8c5026b5e892f88e6ed655fa34edb7937ec13ecdf45f2749b91
Tx public key: a9fe16c03edb2febff7d382676e344a8841bc710da76ce256bd1b1a5c7b47ea6
Timestamp: 1711485670 Timestamp [UCT]: 2024-03-26 20:41:10 Age [y:d:h:m:s]: 00:355:14:41:09
Block: 986996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254246 RingCT/type: yes/0
Extra: 01a9fe16c03edb2febff7d382676e344a8841bc710da76ce256bd1b1a5c7b47ea602110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1ce2ad174f21806e7b0c615307214297d2c5becf0400aa9d76824090c2579fe 0.600000000000 1447235 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": 987006, "vin": [ { "gen": { "height": 986996 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1ce2ad174f21806e7b0c615307214297d2c5becf0400aa9d76824090c2579fe" } } ], "extra": [ 1, 169, 254, 22, 192, 62, 219, 47, 235, 255, 125, 56, 38, 118, 227, 68, 168, 132, 27, 199, 16, 218, 118, 206, 37, 107, 209, 177, 165, 199, 180, 126, 166, 2, 17, 0, 0, 0, 12, 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