Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe961d3f1e454a6c35b7c49a8e7f2cb4557daffc518f0568815f47eb3f8722ca

Tx prefix hash: 64a5add0677fe4865fbf24ec17fba87952501c17224f5382465166e0e780cb57
Tx public key: 627fadc0bd65edc3a8fe50e6716166a0a83f9c993600d2f9b0d26df4e7e44ee2
Timestamp: 1770564891 Timestamp [UTC]: 2026-02-08 15:34:51 Age [y:d:h:m:s]: 00:001:01:39:38
Block: 1473446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 770 RingCT/type: yes/0
Extra: 01627fadc0bd65edc3a8fe50e6716166a0a83f9c993600d2f9b0d26df4e7e44ee202086abf98518ab8d953

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 65df56e0d1b5dcbef1b5bb50a9185d2773291857cab7500e1b53e78474c95f6d 0.000600000000 1962728 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": 1473456, "vin": [ { "gen": { "height": 1473446 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65df56e0d1b5dcbef1b5bb50a9185d2773291857cab7500e1b53e78474c95f6d" } } ], "extra": [ 1, 98, 127, 173, 192, 189, 101, 237, 195, 168, 254, 80, 230, 113, 97, 102, 160, 168, 63, 156, 153, 54, 0, 210, 249, 176, 210, 109, 244, 231, 228, 78, 226, 2, 8, 106, 191, 152, 81, 138, 184, 217, 83 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369