Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47e7f99a6e2ab31ab4db233f27ad9533257246aa3cb09c2105e55e1cf02e35e9

Tx prefix hash: 4469160049acad0e320ec0688b0c2e1a488028d3849c6094ae1677380d0e85b1
Tx public key: a19f2d4e27adc5463bf1f67ae3d7d7ed64f81069dfadd2c84fda94dc6845fa58
Timestamp: 1752261646 Timestamp [UTC]: 2025-07-11 19:20:46 Age [y:d:h:m:s]: 01:127:23:20:37
Block: 1323436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356398 RingCT/type: yes/0
Extra: 01a19f2d4e27adc5463bf1f67ae3d7d7ed64f81069dfadd2c84fda94dc6845fa5802110000000143846d66000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 80211f0b754e4c4d51e409c2303da39c06ae312d98124c607066fcf77e117dc4 0.000600000000 1811173 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": 1323446, "vin": [ { "gen": { "height": 1323436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80211f0b754e4c4d51e409c2303da39c06ae312d98124c607066fcf77e117dc4" } } ], "extra": [ 1, 161, 159, 45, 78, 39, 173, 197, 70, 59, 241, 246, 122, 227, 215, 215, 237, 100, 248, 16, 105, 223, 173, 210, 200, 79, 218, 148, 220, 104, 69, 250, 88, 2, 17, 0, 0, 0, 1, 67, 132, 109, 102, 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: