Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d40e30caca6cbbdbc14a0c7975c35cfafd1e251c0740a362be70fff6f0d59abc

Tx prefix hash: fb64cd4d7e0dcfedd79301b2d29b88a1f93e461d096b45234a560fced3a2cdb2
Tx public key: 989d68da6bd227bcb1fb9356594856230bd99b7c66f2acb2a97857f989996ecd
Timestamp: 1771802826 Timestamp [UTC]: 2026-02-22 23:27:06 Age [y:d:h:m:s]: 00:269:13:18:42
Block: 1483676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198216 RingCT/type: yes/0
Extra: 01989d68da6bd227bcb1fb9356594856230bd99b7c66f2acb2a97857f989996ecd021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: baca5064d25eb8f147f1ea954bf2d24bc6b20b1d46bc091b8dcdaa10c209ae2a 0.000600000000 1973086 of 15 -

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": 1483686, "vin": [ { "gen": { "height": 1483676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "baca5064d25eb8f147f1ea954bf2d24bc6b20b1d46bc091b8dcdaa10c209ae2a" } } ], "extra": [ 1, 152, 157, 104, 218, 107, 210, 39, 188, 177, 251, 147, 86, 89, 72, 86, 35, 11, 217, 155, 124, 102, 242, 172, 178, 169, 120, 87, 249, 137, 153, 110, 205, 2, 17, 0, 0, 0, 2, 228, 245, 25, 63, 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: