Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3faed6aa4b82c4fddb7bd14cf405cf464913d4922ec354746eb619daac2d6bc3

Tx prefix hash: 32ef57ff53b95a129406e863c940c06eb19d57abbf014aeecbd8c6b50ac848bf
Tx public key: d8208087bba8a785ce9aa5fe9f404ca80c3651b1c230f80d6603d8a63b022a6c
Timestamp: 1697921306 Timestamp [UCT]: 2023-10-21 20:48:26 Age [y:d:h:m:s]: 01:189:04:06:16
Block: 874711 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396240 RingCT/type: yes/0
Extra: 01d8208087bba8a785ce9aa5fe9f404ca80c3651b1c230f80d6603d8a63b022a6c02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.775745683000 dcy

stealth address amount amount idx
00: 0389fd406911dbc6a590eae87363de661c06146728bf560e4f110e78a6037877 0.775745683000 1329937 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": 874721, "vin": [ { "gen": { "height": 874711 } } ], "vout": [ { "amount": 775745683, "target": { "key": "0389fd406911dbc6a590eae87363de661c06146728bf560e4f110e78a6037877" } } ], "extra": [ 1, 216, 32, 128, 135, 187, 168, 167, 133, 206, 154, 165, 254, 159, 64, 76, 168, 12, 54, 81, 177, 194, 48, 248, 13, 102, 3, 216, 166, 59, 2, 42, 108, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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