Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 780e1fae906a0855d910f83b491fc1a7f40fba1281bd30179aa99e7ed1d32bfb

Tx prefix hash: 8eb44572808a5a23431f5e536d1d421b77c5be8c6df086ba63ad21a4689905cc
Tx public key: f464775402007cece22c65d1ae15a85b168416e9e5f193874100295c131f69c9
Timestamp: 1676160996 Timestamp [UTC]: 2023-02-12 00:16:36 Age [y:d:h:m:s]: 03:284:19:55:01
Block: 695001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 989149 RingCT/type: yes/0
Extra: 01f464775402007cece22c65d1ae15a85b168416e9e5f193874100295c131f69c90211000000025029cbac000000000000000000

1 output(s) for total of 0.003056138971 xmr

stealth address amount amount idx tag
00: fefc462a4188ccd323143fd0c5d2a6cb7954e828ebb58eab6931d791b45fd714 0.003056138971 1137942 of 0 -

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": 695011, "vin": [ { "gen": { "height": 695001 } } ], "vout": [ { "amount": 3056138971, "target": { "key": "fefc462a4188ccd323143fd0c5d2a6cb7954e828ebb58eab6931d791b45fd714" } } ], "extra": [ 1, 244, 100, 119, 84, 2, 0, 124, 236, 226, 44, 101, 209, 174, 21, 168, 91, 22, 132, 22, 233, 229, 241, 147, 135, 65, 0, 41, 92, 19, 31, 105, 201, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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: