Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2d099b7e7b3bc38810cf556b5a9a64806e84419a9896f6d0d2e71c84e1b63ae

Tx prefix hash: 660da1d82d0e7a779950cb0a042228d3718421138e1ebdadfc7269c98acd7d22
Tx public key: b8a0a5198049b76105161e83853121cabf375763100543beeb1ce6d3269b8388
Timestamp: 1656638095 Timestamp [UTC]: 2022-07-01 01:14:55 Age [y:d:h:m:s]: 04:141:18:23:27
Block: 533989 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1147357 RingCT/type: yes/0
Extra: 01b8a0a5198049b76105161e83853121cabf375763100543beeb1ce6d3269b8388021100000014cb8520c2000000000000000000

1 output(s) for total of 0.010439337283 xmr

stealth address amount amount idx tag
00: dc19767165e178cb501bcb5a2999d262ce3f67ddda637f9accc93d7da7c8f4a9 0.010439337283 963384 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": 533999, "vin": [ { "gen": { "height": 533989 } } ], "vout": [ { "amount": 10439337283, "target": { "key": "dc19767165e178cb501bcb5a2999d262ce3f67ddda637f9accc93d7da7c8f4a9" } } ], "extra": [ 1, 184, 160, 165, 25, 128, 73, 183, 97, 5, 22, 30, 131, 133, 49, 33, 202, 191, 55, 87, 99, 16, 5, 67, 190, 235, 28, 230, 211, 38, 155, 131, 136, 2, 17, 0, 0, 0, 20, 203, 133, 32, 194, 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: