Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b73baf499731e9dcdd9381713b6f91d05afa65ca20a7822fe85aab07893caa9e

Tx prefix hash: c3f9ab990d7f26fabed48457c572129041146b83cf90915ffe6fd6f8a4733f6c
Tx public key: 63b1db962d54447cb8262eb995127a9cf329af5304e8525b2ef434f0af6d2d42
Timestamp: 1738719182 Timestamp [UTC]: 2025-02-05 01:33:02 Age [y:d:h:m:s]: 01:103:15:44:37
Block: 1212309 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326094 RingCT/type: yes/0
Extra: 0163b1db962d54447cb8262eb995127a9cf329af5304e8525b2ef434f0af6d2d420211000000041f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c767924a0093b96ddfaf4c1d2a47d526004a384ab2e0fc272d5f64b63d0963c5 0.000600000000 1699080 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": 1212319, "vin": [ { "gen": { "height": 1212309 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c767924a0093b96ddfaf4c1d2a47d526004a384ab2e0fc272d5f64b63d0963c5" } } ], "extra": [ 1, 99, 177, 219, 150, 45, 84, 68, 124, 184, 38, 46, 185, 149, 18, 122, 156, 243, 41, 175, 83, 4, 232, 82, 91, 46, 244, 52, 240, 175, 109, 45, 66, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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: