Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6fb62f64b17b8391e250de87eadfcb7994b3672d79c5ad38ad2e41594134894

Tx prefix hash: c32d16a281f0983c2be686743f69d701c4a9424bfe7867c59c702f4eedefd908
Tx public key: fce91dcd0d861304fff975b2793a8a5b5b42a172505c28603f2b846a2714eba0
Timestamp: 1694219497 Timestamp [UTC]: 2023-09-09 00:31:37 Age [y:d:h:m:s]: 02:147:21:00:35
Block: 844002 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 625318 RingCT/type: yes/0
Extra: 01fce91dcd0d861304fff975b2793a8a5b5b42a172505c28603f2b846a2714eba00211000000064b8f5122000000000000000000

1 output(s) for total of 0.000980553011 xmr

stealth address amount amount idx tag
00: 8880980b38661a9f9fab546a4bcb67e09d88c8b5a75021ad192ad2df05346e03 0.000980553011 1297284 of 0 -

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": 844012, "vin": [ { "gen": { "height": 844002 } } ], "vout": [ { "amount": 980553011, "target": { "key": "8880980b38661a9f9fab546a4bcb67e09d88c8b5a75021ad192ad2df05346e03" } } ], "extra": [ 1, 252, 233, 29, 205, 13, 134, 19, 4, 255, 249, 117, 178, 121, 58, 138, 91, 91, 66, 161, 114, 80, 92, 40, 96, 63, 43, 132, 106, 39, 20, 235, 160, 2, 17, 0, 0, 0, 6, 75, 143, 81, 34, 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) | dinastycoin version: tesla-369