Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b2eec8ef0ace3a1e6305e505bccfc6933f7c12b2b1b08f68377fde1daee87f7

Tx prefix hash: bcfcdc49cc10a98f8ffd2b6c347b4c65c1b0d1fce1f46e304b37f72e9b1c47c4
Tx public key: e1e5854815f0e5e51e3e399dd5f0a70690f0db8165925e9847bb5fa7822454ac
Timestamp: 1756981661 Timestamp [UTC]: 2025-09-04 10:27:41 Age [y:d:h:m:s]: 01:071:21:29:43
Block: 1361117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317635 RingCT/type: yes/0
Extra: 01e1e5854815f0e5e51e3e399dd5f0a70690f0db8165925e9847bb5fa7822454ac021100000002ad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1a2bd88004714fdd2115432f555dffbae10aef415f344a5a509a31cc8e07e502 0.000600000000 1849130 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": 1361127, "vin": [ { "gen": { "height": 1361117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a2bd88004714fdd2115432f555dffbae10aef415f344a5a509a31cc8e07e502" } } ], "extra": [ 1, 225, 229, 133, 72, 21, 240, 229, 229, 30, 62, 57, 157, 213, 240, 167, 6, 144, 240, 219, 129, 101, 146, 94, 152, 71, 187, 95, 167, 130, 36, 84, 172, 2, 17, 0, 0, 0, 2, 173, 121, 72, 208, 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: