Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 376a2e4d265b042d42d972c5358b1b502733787e2bdbeefa3904e5dde00f7b84

Tx prefix hash: fc32af0191cc55760df80315476ddcfe7e86c9574a2e67518d296594e13d4a23
Tx public key: 2fb14d5c50bfbaba4aadd0376ab0fd68f7e887061973c3dc5574aa7a5fe9d712
Timestamp: 1718701684 Timestamp [UCT]: 2024-06-18 09:08:04 Age [y:d:h:m:s]: 00:208:14:57:06
Block: 1046798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149279 RingCT/type: yes/0
Extra: 012fb14d5c50bfbaba4aadd0376ab0fd68f7e887061973c3dc5574aa7a5fe9d7120211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb669cb8f128bda8dd55985bb6b9715dd32fb02f5c2a12f63b0506200f2bab48 0.600000000000 1516617 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": 1046808, "vin": [ { "gen": { "height": 1046798 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb669cb8f128bda8dd55985bb6b9715dd32fb02f5c2a12f63b0506200f2bab48" } } ], "extra": [ 1, 47, 177, 77, 92, 80, 191, 186, 186, 74, 173, 208, 55, 106, 176, 253, 104, 247, 232, 135, 6, 25, 115, 195, 220, 85, 116, 170, 122, 95, 233, 215, 18, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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