Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f368e09e664b324c3c9de8e1075212fb5f0eefa00a6f060251ad4f2c1a13512

Tx prefix hash: 5574666da5fda1e02aa4fea2eb3964ed8cc6c6b004187897e099f50b2fb7be8e
Tx public key: 30acfc9ead465fe90cfb980ff05acbca6c3c21d1d709509c57a91fe5263e5906
Timestamp: 1773439322 Timestamp [UTC]: 2026-03-13 22:02:02 Age [y:d:h:m:s]: 00:247:19:08:11
Block: 1497213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182572 RingCT/type: yes/0
Extra: 0130acfc9ead465fe90cfb980ff05acbca6c3c21d1d709509c57a91fe5263e5906021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 43fbe8fde21522b6d36ed7f3f8cd4c6e47d8e31b86c470f1477d4f31d85bc67e 0.000600000000 1986847 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": 1497223, "vin": [ { "gen": { "height": 1497213 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43fbe8fde21522b6d36ed7f3f8cd4c6e47d8e31b86c470f1477d4f31d85bc67e" } } ], "extra": [ 1, 48, 172, 252, 158, 173, 70, 95, 233, 12, 251, 152, 15, 240, 90, 203, 202, 108, 60, 33, 209, 215, 9, 80, 156, 87, 169, 31, 229, 38, 62, 89, 6, 2, 17, 0, 0, 0, 1, 228, 245, 25, 63, 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: