Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a44c576d6ae1fc0da0f1fa0b04089b0d9cddf04f465072b7ecf4a588608b21e

Tx prefix hash: fb85fbf805467e3e0a311bb7874a9bf7b3cfb5508d660d3ca0b67394c36a586a
Tx public key: d1d57246da2defd97f098d7318fbe5786ea7a6844c92afb780a60be6dd74f58a
Timestamp: 1771738806 Timestamp [UTC]: 2026-02-22 05:40:06 Age [y:d:h:m:s]: 00:270:00:58:51
Block: 1483148 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198551 RingCT/type: yes/0
Extra: 01d1d57246da2defd97f098d7318fbe5786ea7a6844c92afb780a60be6dd74f58a021100000009e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2a05f13a9351b0ad723865333f700a706e0259b45cb041357ab946da9e22f55f 0.000600000000 1972552 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": 1483158, "vin": [ { "gen": { "height": 1483148 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a05f13a9351b0ad723865333f700a706e0259b45cb041357ab946da9e22f55f" } } ], "extra": [ 1, 209, 213, 114, 70, 218, 45, 239, 217, 127, 9, 141, 115, 24, 251, 229, 120, 110, 167, 166, 132, 76, 146, 175, 183, 128, 166, 11, 230, 221, 116, 245, 138, 2, 17, 0, 0, 0, 9, 228, 245, 25, 63, 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: