Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4dc632f5db14d7832e7a2a661c7331edaaf2c6b15c22e9d3ad4c7c1e8915c500

Tx prefix hash: 850ed51ce23bf72976dcc7a7a99c92f7a259fd2a5f5b7fdecbd58f3900bebfb0
Tx public key: c490836a7a245c0ad8fb554c84738cd7016f58b68427f3ace12ce3a0f1ab0d2e
Timestamp: 1656938832 Timestamp [UTC]: 2022-07-04 12:47:12 Age [y:d:h:m:s]: 04:141:04:17:50
Block: 536472 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1147022 RingCT/type: yes/0
Extra: 01c490836a7a245c0ad8fb554c84738cd7016f58b68427f3ace12ce3a0f1ab0d2e0211000000012e6b1fd5000000000000000000

1 output(s) for total of 0.010243437359 xmr

stealth address amount amount idx tag
00: cf56534018005b47799124c4782a58150ce56fd8091c5aac64e0a0df0f3c4aa5 0.010243437359 966239 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": 536482, "vin": [ { "gen": { "height": 536472 } } ], "vout": [ { "amount": 10243437359, "target": { "key": "cf56534018005b47799124c4782a58150ce56fd8091c5aac64e0a0df0f3c4aa5" } } ], "extra": [ 1, 196, 144, 131, 106, 122, 36, 92, 10, 216, 251, 85, 76, 132, 115, 140, 215, 1, 111, 88, 182, 132, 39, 243, 172, 225, 44, 227, 160, 241, 171, 13, 46, 2, 17, 0, 0, 0, 1, 46, 107, 31, 213, 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: