Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 017506da875e78de4e855c29b68d0bdcba9290bc4a279d84a2834e49fcfb7d2b

Tx prefix hash: 8e91f4f9c3e99ddf30c9809e2582ec416120d24c7a798a2060438613c70650c2
Tx public key: fb251b7e1e540a4cce8798010290b1d07b1f5eaa4945d3188c06e9902f7688db
Timestamp: 1773470245 Timestamp [UTC]: 2026-03-14 06:37:25 Age [y:d:h:m:s]: 00:243:05:15:16
Block: 1497463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179141 RingCT/type: yes/0
Extra: 01fb251b7e1e540a4cce8798010290b1d07b1f5eaa4945d3188c06e9902f7688db021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5483e5d0b4d4f9cf2409e38aae4c10a66cf768ccc256ec007aa5c25d04abd63d 0.000600000000 1987099 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": 1497473, "vin": [ { "gen": { "height": 1497463 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5483e5d0b4d4f9cf2409e38aae4c10a66cf768ccc256ec007aa5c25d04abd63d" } } ], "extra": [ 1, 251, 37, 27, 126, 30, 84, 10, 76, 206, 135, 152, 1, 2, 144, 177, 208, 123, 31, 94, 170, 73, 69, 211, 24, 140, 6, 233, 144, 47, 118, 136, 219, 2, 17, 0, 0, 0, 1, 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: