Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41b6b13bbfbb8be5504faec5b93a2da6467d5f7cc0ddfbdbd144110a334dbe80

Tx prefix hash: 0149c3285b66dd7e9111a3e5af2fbe4104040502a950c60fe534b4db410673fd
Tx public key: e1e66f3540f977e50e94c17f221ceeab606978808755bd201e0c6a31959cb90a
Timestamp: 1772047697 Timestamp [UTC]: 2026-02-25 19:28:17 Age [y:d:h:m:s]: 00:262:12:49:37
Block: 1485736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193026 RingCT/type: yes/0
Extra: 01e1e66f3540f977e50e94c17f221ceeab606978808755bd201e0c6a31959cb90a021100000015f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fb7c2500f6432c75e796461bd1a56cd3abaaa1abe22cfcb32f0a4a3c6728ca0d 0.000600000000 1975174 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": 1485746, "vin": [ { "gen": { "height": 1485736 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb7c2500f6432c75e796461bd1a56cd3abaaa1abe22cfcb32f0a4a3c6728ca0d" } } ], "extra": [ 1, 225, 230, 111, 53, 64, 249, 119, 229, 14, 148, 193, 127, 34, 28, 238, 171, 96, 105, 120, 128, 135, 85, 189, 32, 30, 12, 106, 49, 149, 156, 185, 10, 2, 17, 0, 0, 0, 21, 241, 136, 200, 168, 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: