Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c95f7ac644e2b798665ed95b898425799bca263ce35afaea1271e8c7bca4caa1

Tx prefix hash: c4926667dd31e0aa8ab568f59710597b24af555ac2d23e0fb0f9f252bb207b94
Tx public key: bb59ca0fc58e724409a6d23ec44ae5eccf413342d197db7471847b5854e5429e
Timestamp: 1751123555 Timestamp [UTC]: 2025-06-28 15:12:35 Age [y:d:h:m:s]: 01:056:02:55:10
Block: 1314591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304791 RingCT/type: yes/0
Extra: 01bb59ca0fc58e724409a6d23ec44ae5eccf413342d197db7471847b5854e5429e021100000002a11dba98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c68af8eb04730a114a95fcefc8d9afddfb997f1f0b0a08bb381340a0fb846f5a 0.000600000000 1802240 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": 1314601, "vin": [ { "gen": { "height": 1314591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c68af8eb04730a114a95fcefc8d9afddfb997f1f0b0a08bb381340a0fb846f5a" } } ], "extra": [ 1, 187, 89, 202, 15, 197, 142, 114, 68, 9, 166, 210, 62, 196, 74, 229, 236, 207, 65, 51, 66, 209, 151, 219, 116, 113, 132, 123, 88, 84, 229, 66, 158, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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: