Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bf3a4a435faedc6770768c911dad3b9772d66f73a36b8e01c9f008f8a7eb764

Tx prefix hash: d4ba023f9200bae44ffffe7c5259b295314b565d56432d8540e3b4885fe659ef
Tx public key: 0348a756953d69ded726d6aaa9a608eb7967fcb63fd58cb130d19fa235ee6a22
Timestamp: 1650685504 Timestamp [UTC]: 2022-04-23 03:45:04 Age [y:d:h:m:s]: 04:211:09:54:46
Block: 486127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1195801 RingCT/type: yes/0
Extra: 010348a756953d69ded726d6aaa9a608eb7967fcb63fd58cb130d19fa235ee6a2202110000000133af99f4000000000000000000

1 output(s) for total of 0.015040409954 xmr

stealth address amount amount idx tag
00: 0b4f67049413c27c7e7c86fe05f1f6bfa7f0036d1b67e37637f69e681dd185bf 0.015040409954 908342 of 0 -

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": 486137, "vin": [ { "gen": { "height": 486127 } } ], "vout": [ { "amount": 15040409954, "target": { "key": "0b4f67049413c27c7e7c86fe05f1f6bfa7f0036d1b67e37637f69e681dd185bf" } } ], "extra": [ 1, 3, 72, 167, 86, 149, 61, 105, 222, 215, 38, 214, 170, 169, 166, 8, 235, 121, 103, 252, 182, 63, 213, 140, 177, 48, 209, 159, 162, 53, 238, 106, 34, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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: