Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f26e3b9533e07cf247dbd2e6b042b8d517743e2637b2c5aca4323938543db111

Tx prefix hash: b05cff82dabf1af8a6dce5d0d7329ba0764bfb1f5c26feb5430b6dfba8213c7e
Tx public key: 54a5da8af029591e39cfbb090cadf4308965f488e7220b677a7d07e0870a6221
Timestamp: 1773521465 Timestamp [UTC]: 2026-03-14 20:51:05 Age [y:d:h:m:s]: 00:245:15:07:08
Block: 1497898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180976 RingCT/type: yes/0
Extra: 0154a5da8af029591e39cfbb090cadf4308965f488e7220b677a7d07e0870a6221021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 10f1f2a73b3f370823aec1736bd58add96ac7b1700bfebae25cb0079c294a48d 0.000600000000 1987542 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": 1497908, "vin": [ { "gen": { "height": 1497898 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10f1f2a73b3f370823aec1736bd58add96ac7b1700bfebae25cb0079c294a48d" } } ], "extra": [ 1, 84, 165, 218, 138, 240, 41, 89, 30, 57, 207, 187, 9, 12, 173, 244, 48, 137, 101, 244, 136, 231, 34, 11, 103, 122, 125, 7, 224, 135, 10, 98, 33, 2, 17, 0, 0, 0, 2, 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: