Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c23b8e7b10c573668b0f54c835325a894e96820b5da412717befb06c364b5df

Tx prefix hash: cf57429367d19d2d1a357f817a798908a63c888ffc52f0daab2e192f9df40f37
Tx public key: acc6d6a265d4a94ea61a30599a79881f4a77dbaaf0651bd026ef99a1e6d415df
Timestamp: 1578889619 Timestamp [UTC]: 2020-01-13 04:26:59 Age [y:d:h:m:s]: 06:127:02:20:58
Block: 44362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1492120 RingCT/type: yes/0
Extra: 01acc6d6a265d4a94ea61a30599a79881f4a77dbaaf0651bd026ef99a1e6d415df0211000000264943cd9f000000000000000000

1 output(s) for total of 0.437533307642 xmr

stealth address amount amount idx tag
00: 9aaa9c140233bad21f8e0fc700d07b9aad5b884a31d262ea7359b03af740cf3f 0.437533307642 80712 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": 44372, "vin": [ { "gen": { "height": 44362 } } ], "vout": [ { "amount": 437533307642, "target": { "key": "9aaa9c140233bad21f8e0fc700d07b9aad5b884a31d262ea7359b03af740cf3f" } } ], "extra": [ 1, 172, 198, 214, 162, 101, 212, 169, 78, 166, 26, 48, 89, 154, 121, 136, 31, 74, 119, 219, 170, 240, 101, 27, 208, 38, 239, 153, 161, 230, 212, 21, 223, 2, 17, 0, 0, 0, 38, 73, 67, 205, 159, 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: