Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d0dc8cd642d86151794b15048421e828aaa0164e2a8aa1e029d23eec6563c9c

Tx prefix hash: 3f966cde17ec1b73622d446725b00da0d47a61305f705b2cb14e50bd4a0fe859
Tx public key: f927901f287bcc0cee65a59eea2487132d6f1b5185e01017fe7fdc7d9c8c27a2
Timestamp: 1709077068 Timestamp [UTC]: 2024-02-27 23:37:48 Age [y:d:h:m:s]: 02:267:20:36:58
Block: 966998 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 716496 RingCT/type: yes/0
Extra: 01f927901f287bcc0cee65a59eea2487132d6f1b5185e01017fe7fdc7d9c8c27a202110000000352d47e94000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6cd6fc55e6b306de8ab9fe3939b3198e92a3f23694de6584959e0c1b33bda934 0.000600000000 1426769 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": 967008, "vin": [ { "gen": { "height": 966998 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6cd6fc55e6b306de8ab9fe3939b3198e92a3f23694de6584959e0c1b33bda934" } } ], "extra": [ 1, 249, 39, 144, 31, 40, 123, 204, 12, 238, 101, 165, 158, 234, 36, 135, 19, 45, 111, 27, 81, 133, 224, 16, 23, 254, 127, 220, 125, 156, 140, 39, 162, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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: