Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7052c434ebde7e5909138637ffbda885d2dc116949c8302e10169c3a48e87dcd

Tx prefix hash: 56c6a6c256851de6ddd9b870df862923cca87f93405ecb02540d952c2202d3ea
Tx public key: 6401875701f8aa765f1acde6b360ad708708723dcfa39c0ad509f8a271e2753c
Timestamp: 1758204931 Timestamp [UTC]: 2025-09-18 14:15:31 Age [y:d:h:m:s]: 01:064:06:23:22
Block: 1371186 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312308 RingCT/type: yes/0
Extra: 016401875701f8aa765f1acde6b360ad708708723dcfa39c0ad509f8a271e2753c021100000001ad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2e796c2ec9cde8cbfbfdb9bde37ff22e194e28a208229e2e4c005c90f329cd60 0.000600000000 1859263 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": 1371196, "vin": [ { "gen": { "height": 1371186 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e796c2ec9cde8cbfbfdb9bde37ff22e194e28a208229e2e4c005c90f329cd60" } } ], "extra": [ 1, 100, 1, 135, 87, 1, 248, 170, 118, 95, 26, 205, 230, 179, 96, 173, 112, 135, 8, 114, 61, 207, 163, 156, 10, 213, 9, 248, 162, 113, 226, 117, 60, 2, 17, 0, 0, 0, 1, 173, 121, 72, 208, 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: