Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2c169ce6347e5b4880bd86c317dfc9687b91f8b7d0445c0b2cb2089c0e4c7ba

Tx prefix hash: 0436c5e8d89ba04a15520ff556234583c4cdb88508762742445782d2211ab7ca
Tx public key: 54d5239119347678b68105da21abac67ea3dbe81ba7b0088858d510dcc4cae28
Timestamp: 1588733105 Timestamp [UCT]: 2020-05-06 02:45:05 Age [y:d:h:m:s]: 04:195:07:17:35
Block: 98592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1056300 RingCT/type: yes/0
Extra: 0154d5239119347678b68105da21abac67ea3dbe81ba7b0088858d510dcc4cae28021100000002a86a1a65000000000000000000

1 output(s) for total of 289.284084296000 dcy

stealth address amount amount idx
00: 7b2e7b783354b8ea8b4fa474f7438f9a1b0714fabf9b21fa3b1ca8ddbadaefd2 289.284084296000 174284 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": 98602, "vin": [ { "gen": { "height": 98592 } } ], "vout": [ { "amount": 289284084296, "target": { "key": "7b2e7b783354b8ea8b4fa474f7438f9a1b0714fabf9b21fa3b1ca8ddbadaefd2" } } ], "extra": [ 1, 84, 213, 35, 145, 25, 52, 118, 120, 182, 129, 5, 218, 33, 171, 172, 103, 234, 61, 190, 129, 186, 123, 0, 136, 133, 141, 81, 13, 204, 76, 174, 40, 2, 17, 0, 0, 0, 2, 168, 106, 26, 101, 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