Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a28fe35d7a106cbe201158c817f8b9d77d8c8e9ea39756eec4e11ad312ec21f9

Tx prefix hash: bf6bc1e90780e61c67a39ca6554a254656467ccab2776cbcbde9f0f14fb6df8b
Tx public key: 3afc63e6b293610ee9f3f7a7af77c0367e026bd5cc734fc008f9c9b5adfcaf0f
Timestamp: 1732170255 Timestamp [UTC]: 2024-11-21 06:24:15 Age [y:d:h:m:s]: 01:359:16:11:08
Block: 1158351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 520858 RingCT/type: yes/0
Extra: 013afc63e6b293610ee9f3f7a7af77c0367e026bd5cc734fc008f9c9b5adfcaf0f021100000006007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 62cf0a6fc50c81777447a61f0c1fd796a81ed6f9cc8af199f91393e62ab5a63f 0.000600000000 1643980 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": 1158361, "vin": [ { "gen": { "height": 1158351 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62cf0a6fc50c81777447a61f0c1fd796a81ed6f9cc8af199f91393e62ab5a63f" } } ], "extra": [ 1, 58, 252, 99, 230, 178, 147, 97, 14, 233, 243, 247, 167, 175, 119, 192, 54, 126, 2, 107, 213, 204, 115, 79, 192, 8, 249, 201, 181, 173, 252, 175, 15, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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: