Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfbc79cd350937b5e6b2fc9e05f8c04e5650c927a2cae06314b39e83ffc4dfea

Tx prefix hash: 508fbd8283780b698023252fe75a7550cc1d9e1c03f17bb5aecab42704889281
Tx public key: cf5ff239925fd25390a373eb89853355bcc26a48ad1b854fd2a87b3cf677e9af
Timestamp: 1742643645 Timestamp [UTC]: 2025-03-22 11:40:45 Age [y:d:h:m:s]: 01:242:08:44:32
Block: 1244804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 437335 RingCT/type: yes/0
Extra: 01cf5ff239925fd25390a373eb89853355bcc26a48ad1b854fd2a87b3cf677e9af021100000002af845649000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a8fd195e8e9b38d3dcbdc1aaccf1b60340ea2eb29d67924e5f5e798ef7db3347 0.000600000000 1731795 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": 1244814, "vin": [ { "gen": { "height": 1244804 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8fd195e8e9b38d3dcbdc1aaccf1b60340ea2eb29d67924e5f5e798ef7db3347" } } ], "extra": [ 1, 207, 95, 242, 57, 146, 95, 210, 83, 144, 163, 115, 235, 137, 133, 51, 85, 188, 194, 106, 72, 173, 27, 133, 79, 210, 168, 123, 60, 246, 119, 233, 175, 2, 17, 0, 0, 0, 2, 175, 132, 86, 73, 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: