Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0876dd1b2745a064405295bb0aa8aa252f06c46daea01111b0df5a14bbf6e8f6

Tx prefix hash: 3f46127141d972dbe06e75ef0c34742a322049342ba13f5f4ea18ef5c995a997
Tx public key: 17f7134b9561352fe593adc98bb444ce1ff077e4e4790916b4d0c19696566f89
Timestamp: 1741963135 Timestamp [UTC]: 2025-03-14 14:38:55 Age [y:d:h:m:s]: 01:247:12:26:28
Block: 1239187 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 440915 RingCT/type: yes/0
Extra: 0117f7134b9561352fe593adc98bb444ce1ff077e4e4790916b4d0c19696566f890211000000081f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3edc2660dd6f160a1b3055662ee0e112a40d7eaf7d15ab0f1981d4d4a4125968 0.000600000000 1726152 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": 1239197, "vin": [ { "gen": { "height": 1239187 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3edc2660dd6f160a1b3055662ee0e112a40d7eaf7d15ab0f1981d4d4a4125968" } } ], "extra": [ 1, 23, 247, 19, 75, 149, 97, 53, 47, 229, 147, 173, 201, 139, 180, 68, 206, 31, 240, 119, 228, 228, 121, 9, 22, 180, 208, 193, 150, 150, 86, 111, 137, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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: