Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f31da63c274b9178ae0918dce2e27aaab3ff1eb5534581369d4200c1300e6764

Tx prefix hash: 765a1d69805124f6035984d4bc92451eb7f5480652e1b27d6b7e02cf6b4d2ee9
Tx public key: 9d1eead4f40061d3923d741b3001e1ede1160d15e01342ef9dc31f3759e91761
Timestamp: 1747498732 Timestamp [UTC]: 2025-05-17 16:18:52 Age [y:d:h:m:s]: 00:364:10:29:39
Block: 1285000 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250553 RingCT/type: yes/0
Extra: 019d1eead4f40061d3923d741b3001e1ede1160d15e01342ef9dc31f3759e917610211000000069f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2fe35c6d445d98759c8b6a901978c681a7a5f5e5237e58c93f7529165c9bceb5 0.000600000000 1772463 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": 1285010, "vin": [ { "gen": { "height": 1285000 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2fe35c6d445d98759c8b6a901978c681a7a5f5e5237e58c93f7529165c9bceb5" } } ], "extra": [ 1, 157, 30, 234, 212, 244, 0, 97, 211, 146, 61, 116, 27, 48, 1, 225, 237, 225, 22, 13, 21, 224, 19, 66, 239, 157, 195, 31, 55, 89, 233, 23, 97, 2, 17, 0, 0, 0, 6, 159, 159, 230, 140, 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: