Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 119fa96adf7cc2460bd6626977fefbad63c0b26dbaecb02b33e18bbe5989fdfa

Tx prefix hash: 76a09521e393a0118ea0d60285cd79a1275e0da10486ceab5daadb0e3318d716
Tx public key: af470676c469f5ed98a6cf2ce3276b49ef0c6b862bcf0de8cb268c928c9b5407
Timestamp: 1771769060 Timestamp [UTC]: 2026-02-22 14:04:20 Age [y:d:h:m:s]: 00:264:09:46:19
Block: 1483395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194353 RingCT/type: yes/0
Extra: 01af470676c469f5ed98a6cf2ce3276b49ef0c6b862bcf0de8cb268c928c9b5407021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2ad958f33fc00965bc1c3a3a160d71fe3364726635020fd1d5370858d8e133ba 0.000600000000 1972803 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": 1483405, "vin": [ { "gen": { "height": 1483395 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ad958f33fc00965bc1c3a3a160d71fe3364726635020fd1d5370858d8e133ba" } } ], "extra": [ 1, 175, 71, 6, 118, 196, 105, 245, 237, 152, 166, 207, 44, 227, 39, 107, 73, 239, 12, 107, 134, 43, 207, 13, 232, 203, 38, 140, 146, 140, 155, 84, 7, 2, 17, 0, 0, 0, 3, 228, 245, 25, 63, 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: