Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4aa32b5ce3675fb1c0216531e6fc429f30b2deb074cc83928d598c45a287e2d

Tx prefix hash: 8770ac4c5c2e2c813252f0a7129ccd46e34a21148f2e35296112debed10adcb3
Tx public key: 077ba4aa0de7b58bd601d40c00b5239f6f97d20bc5e40dcffd66250808e453ee
Timestamp: 1771734495 Timestamp [UTC]: 2026-02-22 04:28:15 Age [y:d:h:m:s]: 00:270:02:16:21
Block: 1483114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198589 RingCT/type: yes/0
Extra: 01077ba4aa0de7b58bd601d40c00b5239f6f97d20bc5e40dcffd66250808e453ee021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bf0ea5ec1ca3ba32747d4cf62e576222e40ea5676cbe5d4e0e38a4b9afbc3e7f 0.000600000000 1972518 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": 1483124, "vin": [ { "gen": { "height": 1483114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf0ea5ec1ca3ba32747d4cf62e576222e40ea5676cbe5d4e0e38a4b9afbc3e7f" } } ], "extra": [ 1, 7, 123, 164, 170, 13, 231, 181, 139, 214, 1, 212, 12, 0, 181, 35, 159, 111, 151, 210, 11, 197, 228, 13, 207, 253, 102, 37, 8, 8, 228, 83, 238, 2, 17, 0, 0, 0, 3, 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: