Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6823aff3c380e1e68693b0d3830c75d76eb32dc3690c9cecd79bd8bdb649b163

Tx prefix hash: 786e9a5fadb2e2c4f5ae325d8e72a5fda89928b52b9b2ba601c5b73d7200bb25
Tx public key: fd0c08f5a3c8613af609ea89125c452f68fccb24fec0d065aead051e7142bf15
Timestamp: 1741662428 Timestamp [UTC]: 2025-03-11 03:07:08 Age [y:d:h:m:s]: 01:063:01:46:32
Block: 1236692 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295907 RingCT/type: yes/0
Extra: 01fd0c08f5a3c8613af609ea89125c452f68fccb24fec0d065aead051e7142bf15021100000005007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3c0a3b162a41afd4000d6cc2350c5d99827c63f6ac37e73baa56089c5272cb1d 0.000600000000 1723641 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": 1236702, "vin": [ { "gen": { "height": 1236692 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c0a3b162a41afd4000d6cc2350c5d99827c63f6ac37e73baa56089c5272cb1d" } } ], "extra": [ 1, 253, 12, 8, 245, 163, 200, 97, 58, 246, 9, 234, 137, 18, 92, 69, 47, 104, 252, 203, 36, 254, 192, 208, 101, 174, 173, 5, 30, 113, 66, 191, 21, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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: