Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcf6e81a5b41257721da3a30046d7ca9f074d06bdfa8ce32725bb8bfa3368c28

Tx prefix hash: f2a137895362c55cf7b3f8bc18b06bca091a681c60d4f49dd8546088949ca1b3
Tx public key: 4dd4c48673f0709edcd44bdfa7d24c60d380c5625143e02eb337e87df571b0f3
Timestamp: 1704554904 Timestamp [UTC]: 2024-01-06 15:28:24 Age [y:d:h:m:s]: 02:129:03:31:00
Block: 929497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 604312 RingCT/type: yes/0
Extra: 014dd4c48673f0709edcd44bdfa7d24c60d380c5625143e02eb337e87df571b0f302110000000552d47e94000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 30bb3596542ad7d5a23783f6ed5f921d593e5b5c721b000396df68487709e2a9 0.000600000000 1387373 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": 929507, "vin": [ { "gen": { "height": 929497 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30bb3596542ad7d5a23783f6ed5f921d593e5b5c721b000396df68487709e2a9" } } ], "extra": [ 1, 77, 212, 196, 134, 115, 240, 112, 158, 220, 212, 75, 223, 167, 210, 76, 96, 211, 128, 197, 98, 81, 67, 224, 46, 179, 55, 232, 125, 245, 113, 176, 243, 2, 17, 0, 0, 0, 5, 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: