Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9bfee378b8410bf5c593027806e6c2e970e7591d1224f55e04ea645bd6bcb535

Tx prefix hash: fa6561b54a8052ec55e08db92d971e56a0e8fd9d035d3c98e2eca1ae8cf4d8b7
Tx public key: 9f1537d0ed2809071262e88ee6d72ab5e380ebaee790f42ea38ed00034e377be
Timestamp: 1746286424 Timestamp [UTC]: 2025-05-03 15:33:44 Age [y:d:h:m:s]: 01:109:00:33:10
Block: 1274960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342623 RingCT/type: yes/0
Extra: 019f1537d0ed2809071262e88ee6d72ab5e380ebaee790f42ea38ed00034e377be02110000000101491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 544f2da7fc1ad0d2072a86be1f67baac234cfbf8f8c424c6ea06b83bc4e85bb0 0.000600000000 1762261 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": 1274970, "vin": [ { "gen": { "height": 1274960 } } ], "vout": [ { "amount": 600000000, "target": { "key": "544f2da7fc1ad0d2072a86be1f67baac234cfbf8f8c424c6ea06b83bc4e85bb0" } } ], "extra": [ 1, 159, 21, 55, 208, 237, 40, 9, 7, 18, 98, 232, 142, 230, 215, 42, 181, 227, 128, 235, 174, 231, 144, 244, 46, 163, 142, 208, 0, 52, 227, 119, 190, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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: