Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5c14bc8d6efa3cbcee8b19d9e08767791427f3b7e941df3321c1666b6ccf79a

Tx prefix hash: bf8b4fcd3f74cc15ebf464a284fb24bff95db6c5d324a07e885d3ade237fed96
Tx public key: 25f4d8f8cf9db57f179315b598a53da601d9c90b20683889e282923f0021b90d
Timestamp: 1744956743 Timestamp [UTC]: 2025-04-18 06:12:23 Age [y:d:h:m:s]: 01:214:16:41:59
Block: 1263953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417499 RingCT/type: yes/0
Extra: 0125f4d8f8cf9db57f179315b598a53da601d9c90b20683889e282923f0021b90d0211000000012609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 77405bc3e9bcbc2a418f5192d796fee003c187862d5964c7d0eb57f0a283dce1 0.000600000000 1751146 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": 1263963, "vin": [ { "gen": { "height": 1263953 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77405bc3e9bcbc2a418f5192d796fee003c187862d5964c7d0eb57f0a283dce1" } } ], "extra": [ 1, 37, 244, 216, 248, 207, 157, 181, 127, 23, 147, 21, 181, 152, 165, 61, 166, 1, 217, 201, 11, 32, 104, 56, 137, 226, 130, 146, 63, 0, 33, 185, 13, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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: