Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4ac9d373e57e3010502b8701d3b8c849e711f0397696ffb5e9d9775bc92b353

Tx prefix hash: 6e142a90c017cdb9fa97d4989ad5e892112a8166449115405d771a146caf5b43
Tx public key: d62abca927aff45944b5143f6adb7b36112024defbe8e95cc0b14c4bcf36d18a
Timestamp: 1581256780 Timestamp [UCT]: 2020-02-09 13:59:40 Age [y:d:h:m:s]: 05:024:19:00:51
Block: 61444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1170407 RingCT/type: yes/0
Extra: 01d62abca927aff45944b5143f6adb7b36112024defbe8e95cc0b14c4bcf36d18a0211000000084943cd9f000000000000000000

1 output(s) for total of 384.118482065000 dcy

stealth address amount amount idx
00: 7dd019d54acd5d7d36a92d0414af08c984e1dac8e300f742dc4d84b98aabc741 384.118482065000 113232 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": 61454, "vin": [ { "gen": { "height": 61444 } } ], "vout": [ { "amount": 384118482065, "target": { "key": "7dd019d54acd5d7d36a92d0414af08c984e1dac8e300f742dc4d84b98aabc741" } } ], "extra": [ 1, 214, 42, 188, 169, 39, 175, 244, 89, 68, 181, 20, 63, 106, 219, 123, 54, 17, 32, 36, 222, 251, 232, 233, 92, 192, 177, 76, 75, 207, 54, 209, 138, 2, 17, 0, 0, 0, 8, 73, 67, 205, 159, 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