Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1ff0de837c5504a87e5ac3fdcbd0b531a1d6ec99b96cdc4c79681e151684d3d

Tx prefix hash: 3a20933e1328d7bb31001af4ae679379cc36d2d3aee4a6f0f8a810158a818d72
Tx public key: 896f32eb325c29bc144efb631b04fcf06fdd28658b1914de0b953043b0023336
Timestamp: 1749329012 Timestamp [UTC]: 2025-06-07 20:43:32 Age [y:d:h:m:s]: 00:339:15:54:00
Block: 1300157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232685 RingCT/type: yes/0
Extra: 01896f32eb325c29bc144efb631b04fcf06fdd28658b1914de0b953043b002333602110000000743846d66000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4843f70b014d83942bc8c464f4b3e58703dd36704599beae80c28bb196c05e1f 0.000600000000 1787704 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": 1300167, "vin": [ { "gen": { "height": 1300157 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4843f70b014d83942bc8c464f4b3e58703dd36704599beae80c28bb196c05e1f" } } ], "extra": [ 1, 137, 111, 50, 235, 50, 92, 41, 188, 20, 78, 251, 99, 27, 4, 252, 240, 111, 221, 40, 101, 139, 25, 20, 222, 11, 149, 48, 67, 176, 2, 51, 54, 2, 17, 0, 0, 0, 7, 67, 132, 109, 102, 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: