Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6676c942761139ae18d608da5d53ba06cc94cee71b74ed4e33c963ece0d617d7

Tx prefix hash: dfaa59e39e19dde140a4d8f3824463d81455a6f87f87f4c279482706c2339caf
Tx public key: bb00bf0873de814bcb925be9e4e6060ede00d0f4d42da5fb0c311db6a6cbc088
Timestamp: 1769650142 Timestamp [UTC]: 2026-01-29 01:29:02 Age [y:d:h:m:s]: 00:290:19:07:22
Block: 1465856 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213290 RingCT/type: yes/0
Extra: 01bb00bf0873de814bcb925be9e4e6060ede00d0f4d42da5fb0c311db6a6cbc088021100000002215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c8c75fe44abd176fbbbae6ddbe9fd5cbecc5911f50ad5bc4ed413a610c6e7c73 0.000600000000 1955088 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": 1465866, "vin": [ { "gen": { "height": 1465856 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8c75fe44abd176fbbbae6ddbe9fd5cbecc5911f50ad5bc4ed413a610c6e7c73" } } ], "extra": [ 1, 187, 0, 191, 8, 115, 222, 129, 75, 203, 146, 91, 233, 228, 230, 6, 14, 222, 0, 208, 244, 212, 45, 165, 251, 12, 49, 29, 182, 166, 203, 192, 136, 2, 17, 0, 0, 0, 2, 33, 91, 191, 137, 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: