Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a65d3d572730e55ae937e844a8f89d2ffcfbd3c878a7f431249d36b21b9b8afa

Tx prefix hash: 06a8219869a42ecf7cd1952d46a03b0f972f88ce000a5535d0a7ab38a11136ad
Tx public key: 899595737a811d1dbd7d4bf259efd9fff46233cffc816eeded3a0db439a53c7f
Timestamp: 1745845056 Timestamp [UTC]: 2025-04-28 12:57:36 Age [y:d:h:m:s]: 01:204:16:39:10
Block: 1271313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 410359 RingCT/type: yes/0
Extra: 01899595737a811d1dbd7d4bf259efd9fff46233cffc816eeded3a0db439a53c7f0211000000019f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 35eb299776598ad6bf783f2a421ef4beec18eb11c361a305d1a9a20bd7b33bdb 0.000600000000 1758572 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": 1271323, "vin": [ { "gen": { "height": 1271313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35eb299776598ad6bf783f2a421ef4beec18eb11c361a305d1a9a20bd7b33bdb" } } ], "extra": [ 1, 137, 149, 149, 115, 122, 129, 29, 29, 189, 125, 75, 242, 89, 239, 217, 255, 244, 98, 51, 207, 252, 129, 110, 237, 237, 58, 13, 180, 57, 165, 60, 127, 2, 17, 0, 0, 0, 1, 159, 159, 230, 140, 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: