Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffa699b03ef0adf4ee6f0a84cc376f7f921e7e5fa24a262a47dd4a4f8bc0fbf1

Tx prefix hash: 2ed5360e14ff4fee213d2604930854b545eddafebbc51184a8fb64104d469d41
Tx public key: 37f41e157ff57c461cd858c88785f20efbf344a918df7520c4c8c7153159bd1d
Timestamp: 1784010252 Timestamp [UTC]: 2026-07-14 06:24:12 Age [y:d:h:m:s]: 00:126:15:24:51
Block: 1581917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 98752 RingCT/type: yes/0
Extra: 0137f41e157ff57c461cd858c88785f20efbf344a918df7520c4c8c7153159bd1d0208e70a9cce933d0716

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c6b4809da2f0f4e251fb4b8bba5be9b4811326a532e6eaba9f31c57c2503889a 0.000600000000 2071909 of 15 <d2>

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": 1581927, "vin": [ { "gen": { "height": 1581917 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "c6b4809da2f0f4e251fb4b8bba5be9b4811326a532e6eaba9f31c57c2503889a", "view_tag": "d2" } } } ], "extra": [ 1, 55, 244, 30, 21, 127, 245, 124, 70, 28, 216, 88, 200, 135, 133, 242, 14, 251, 243, 68, 169, 24, 223, 117, 32, 196, 200, 199, 21, 49, 89, 189, 29, 2, 8, 231, 10, 156, 206, 147, 61, 7, 22 ], "rct_signatures": { "type": 0 } }


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