Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cbc156613e11835afc81d49def8c5ae51262899bf73bae460360502a7d58010

Tx prefix hash: 1f497e6fd9ddc16962c602a4ff59c05963a7c11f600c588d03f9eeacfce37087
Tx public key: 72baa11f0f33b3137abc2817c202cb8a0f969566b27eccf2988e71d5d59f3f95
Timestamp: 1580268302 Timestamp [UTC]: 2020-01-29 03:25:02 Age [y:d:h:m:s]: 06:221:08:20:24
Block: 54775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1573944 RingCT/type: yes/0
Extra: 0172baa11f0f33b3137abc2817c202cb8a0f969566b27eccf2988e71d5d59f3f95021100000001dcee4b4d000000000000000000

1 output(s) for total of 0.404118295741 xmr

stealth address amount amount idx tag
00: 0d50ac9bb68836ac1a63901d93c16e9f10fa389b5bddee6f5742086bc7b8e7e9 0.404118295741 101257 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": 54785, "vin": [ { "gen": { "height": 54775 } } ], "vout": [ { "amount": 404118295741, "target": { "key": "0d50ac9bb68836ac1a63901d93c16e9f10fa389b5bddee6f5742086bc7b8e7e9" } } ], "extra": [ 1, 114, 186, 161, 31, 15, 51, 179, 19, 122, 188, 40, 23, 194, 2, 203, 138, 15, 150, 149, 102, 178, 126, 204, 242, 152, 142, 113, 213, 213, 159, 63, 149, 2, 17, 0, 0, 0, 1, 220, 238, 75, 77, 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: