Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fda6714621af2e4a3fa612bfd66dc734bd735c50989e75569e8e25e8b10e9191

Tx prefix hash: 6f4d3b8097044ef18e7eca4243e04c6fd9b0ea193a90ff75d690a1511607be80
Tx public key: a5f16677237f42d4c287cebcd81beac3d90e11e90022d86356199f070e062f19
Timestamp: 1774324471 Timestamp [UTC]: 2026-03-24 03:54:31 Age [y:d:h:m:s]: 00:240:01:45:14
Block: 1504525 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177147 RingCT/type: yes/0
Extra: 01a5f16677237f42d4c287cebcd81beac3d90e11e90022d86356199f070e062f19021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0a8785dd60b21d6e2f3295676ae03d3ba51b5858a4124ed60d95cc30fa319a18 0.000600000000 1994249 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": 1504535, "vin": [ { "gen": { "height": 1504525 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a8785dd60b21d6e2f3295676ae03d3ba51b5858a4124ed60d95cc30fa319a18" } } ], "extra": [ 1, 165, 241, 102, 119, 35, 127, 66, 212, 194, 135, 206, 188, 216, 27, 234, 195, 217, 14, 17, 233, 0, 34, 216, 99, 86, 25, 159, 7, 14, 6, 47, 25, 2, 17, 0, 0, 0, 2, 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: