Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddc28bea9019dcb53d07c77951076b341dfe2388bf3dba27e3a8470327870ac2

Tx prefix hash: a749e2accf26b085168327cfdcc6d493613d32c3493c20e88d41904df084bddf
Tx public key: bdd1fbf44db52bde1f10d4fa1853018feb30eec29d856e33fa058b879868b7bc
Timestamp: 1770296405 Timestamp [UTC]: 2026-02-05 13:00:05 Age [y:d:h:m:s]: 00:283:02:06:19
Block: 1471239 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207734 RingCT/type: yes/0
Extra: 01bdd1fbf44db52bde1f10d4fa1853018feb30eec29d856e33fa058b879868b7bc021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8b2fc4d495f7d192065009aca205282bc9b01d61dcc894575cff002b3a4f6f92 0.000600000000 1960511 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": 1471249, "vin": [ { "gen": { "height": 1471239 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b2fc4d495f7d192065009aca205282bc9b01d61dcc894575cff002b3a4f6f92" } } ], "extra": [ 1, 189, 209, 251, 244, 77, 181, 43, 222, 31, 16, 212, 250, 24, 83, 1, 143, 235, 48, 238, 194, 157, 133, 110, 51, 250, 5, 139, 135, 152, 104, 183, 188, 2, 17, 0, 0, 0, 3, 241, 136, 200, 168, 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: