Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 112a879669ee2bdcc379142b994f42e3811c167abffc5baaa9efef23c22100fa

Tx prefix hash: 747d2c6fd8936dac3795ff67277d1403c02e1539b807a9bd56fb6006e8e36f0d
Tx public key: 0fe8aae9a55fc24d375dff14ee990ed3e54ddcfcc56f3d5d3c0050621638d772
Timestamp: 1731976906 Timestamp [UTC]: 2024-11-19 00:41:46 Age [y:d:h:m:s]: 01:364:18:30:34
Block: 1156763 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 524569 RingCT/type: yes/0
Extra: 010fe8aae9a55fc24d375dff14ee990ed3e54ddcfcc56f3d5d3c0050621638d7720211000000041f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6fd53fbed026120c54084f685404c84c9a7949b923ee5ca4e39cbf57eac056af 0.000600000000 1642386 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": 1156773, "vin": [ { "gen": { "height": 1156763 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6fd53fbed026120c54084f685404c84c9a7949b923ee5ca4e39cbf57eac056af" } } ], "extra": [ 1, 15, 232, 170, 233, 165, 95, 194, 77, 55, 93, 255, 20, 238, 153, 14, 211, 229, 77, 220, 252, 197, 111, 61, 93, 60, 0, 80, 98, 22, 56, 215, 114, 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: