Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3dfcfa6823be683626e6826e770286f770bc69978ef8b52bee2fb0047223644

Tx prefix hash: 6b5985b7d4511f074a282d094f06dd4282a16f3c1474541922fb9a4bc93341dc
Tx public key: f48df7415e3e3747c21254c4eceb1abdebc7041538fb8f2422fd48416aecfcb3
Timestamp: 1709387175 Timestamp [UTC]: 2024-03-02 13:46:15 Age [y:d:h:m:s]: 02:262:04:47:44
Block: 969579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 712490 RingCT/type: yes/0
Extra: 01f48df7415e3e3747c21254c4eceb1abdebc7041538fb8f2422fd48416aecfcb302110000000752d47e94000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 90221529264e6d966c4d6fadf77871fd78c7612051d4f865dfcbeea189c9e456 0.000600000000 1429416 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": 969589, "vin": [ { "gen": { "height": 969579 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90221529264e6d966c4d6fadf77871fd78c7612051d4f865dfcbeea189c9e456" } } ], "extra": [ 1, 244, 141, 247, 65, 94, 62, 55, 71, 194, 18, 84, 196, 236, 235, 26, 189, 235, 199, 4, 21, 56, 251, 143, 36, 34, 253, 72, 65, 106, 236, 252, 179, 2, 17, 0, 0, 0, 7, 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: