Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47050da594ea05a6c529d9fed9dd70b87f7a5e65e52ed515f9c221d04392ec1a

Tx prefix hash: 2864d9598b49111d02f0035f3697b6f6dfdc6cdf8894540f1540aa6089e89f17
Tx public key: bf7e5d889f4763d30aa72f094fd0609f770ccc2656a728e622f1fc992266cd51
Timestamp: 1663782582 Timestamp [UTC]: 2022-09-21 17:49:42 Age [y:d:h:m:s]: 04:060:04:50:12
Block: 592806 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1089408 RingCT/type: yes/0
Extra: 01bf7e5d889f4763d30aa72f094fd0609f770ccc2656a728e622f1fc992266cd51021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.006664808984 xmr

stealth address amount amount idx tag
00: e7e4cd28511de4f395edf9249c92c1986d0a6e459056d004c2fd7bd6d0f6f4a6 0.006664808984 1027501 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 dinastycoin-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": 592816, "vin": [ { "gen": { "height": 592806 } } ], "vout": [ { "amount": 6664808984, "target": { "key": "e7e4cd28511de4f395edf9249c92c1986d0a6e459056d004c2fd7bd6d0f6f4a6" } } ], "extra": [ 1, 191, 126, 93, 136, 159, 71, 99, 211, 10, 167, 47, 9, 79, 208, 96, 159, 119, 12, 204, 38, 86, 167, 40, 230, 34, 241, 252, 153, 34, 102, 205, 81, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: