Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 250b43af6f6ed455dafe4d1f454e81cf89cf24dbcfd7d6f3a715f0c6738010cb

Tx prefix hash: ff01cf9bb622a52f36c1d75d6fcf10e97ac76494b67d2ccd0eba989ff74ef7a9
Tx public key: 929d84679d4ecd424ab19c33f1197bdc178aec9a0cd1f54161d1b14a4a33b17e
Timestamp: 1644757631 Timestamp [UTC]: 2022-02-13 13:07:11 Age [y:d:h:m:s]: 04:193:04:07:10
Block: 437747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1182346 RingCT/type: yes/0
Extra: 01929d84679d4ecd424ab19c33f1197bdc178aec9a0cd1f54161d1b14a4a33b17e021100000006cb8520c2000000000000000000

1 output(s) for total of 0.021755184376 xmr

stealth address amount amount idx tag
00: dd6ddfee75b6aa77be2fd4eac00f3791c815ebafceffa319e4d60bd2c5e54f67 0.021755184376 849464 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": 437757, "vin": [ { "gen": { "height": 437747 } } ], "vout": [ { "amount": 21755184376, "target": { "key": "dd6ddfee75b6aa77be2fd4eac00f3791c815ebafceffa319e4d60bd2c5e54f67" } } ], "extra": [ 1, 146, 157, 132, 103, 157, 78, 205, 66, 74, 177, 156, 51, 241, 25, 123, 220, 23, 138, 236, 154, 12, 209, 245, 65, 97, 209, 177, 74, 74, 51, 177, 126, 2, 17, 0, 0, 0, 6, 203, 133, 32, 194, 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: